As a user, I would like to use helm repos to deploy my applications. A helm chart was added to support this usecase. As a user having a chart called helm-update and helm-update repo is confusing. Helm charts were renamed and the tests were updated. As a user having all caps params can be confusing because they are reserved for environment variables. Charts were updated for increased readadbility.
The tasks in this commit were updated at some point to use workspaces instead of
pipeline resources but their readmes still refer to the resources.
This commit updates the readmes to remove mention of pipeline resources and link
out to pipeline's workspaces doc.
Added Git CLI task, this task can be used to run git commands.
Git command need to be passed as a script to the task
Signed-off-by: Divyansh42 <diagrawa@redhat.com>
This task will rebase the branch based
on the user input. Before rebase, if `squashing` of the commits is required,
then it can also be done by the task.
Signed-off-by: Divyansh42 <diagrawa@redhat.com>
This can grow the log pretty big with message that not a lot of people will care
about.
when we show the logs on failure, make sure we are not failing if we can't show
them. Sometime some container may be in "Terminated" state until k8 cleans them
up. (i.e: affinity-assistant) so no need to worry if those are failing/exiting before
showing the next container log.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
The loop in the test runner script that was waiting for all TaskRuns to
complete had a bug where it would break out of the loop as soon as any one of
the TaskRuns completed. The test runner then tries to print the logs for all
TaskRuns (which includes some Running ones) which will sometimes fail e.g. if
the TaskRun's pod is in a PodInitializing state.
Fixes#379
Signed-off-by: Dibyo Mukherjee <dibyo@google.com>
Eventually we want to be able to have Tasks declare what versions they
are compatible with and test against those
(https://github.com/tektoncd/catalog/issues/373) but in the meantime, it
seems reasonable to bump the version every time we do a release (and
even once we have #373, we would want to be running tests against new
versions as well - and this could have the benefit of giving us
information about issues in a release early, before users notice them!)
This task allows you to generate Kythe annotation metadata for a given
Go project. This follows the workspace model as presented by the `git`
Task. The expectation is that any results place in the workspace will be
exported by another Task in the pipeline for remote storage (e.g. GCS,
etc).
(cherry picked from commit 20d449cd43)
Since the "master" branch has been renamed to "main", let's make sure we pin to
a revision and fix if there is other rename going on.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
