The gcs-upload task v0.1, when dealing with folders, uses the "-d"
option by default, which deletes remote files by default. This is
a relatively dangerous choice of default, and it's safer to make
that as an opt-in, as it may result in deletion of a lot of remote
files by accident.
V0.2 has a new parameter "deleteExtraFiles" which corresponds to
gsutil "-d" flag. deleteExtraFiles defaults to false, making the
default behaviour of the task different from v0.1.
V0.2 replaces parameters in the script with environment variables
for security as recommended in the catalog best practices.
The cloud-sdk image version has been updated to 390.0.0-slim which
is newer, ~60% smaller than the current image and includes gsutil.
Signed-off-by: Andrea Frittoli <andrea.frittoli@gmail.com>
Currently the readme says the default `gcloud-image` uses the `slim` tag. However, doing a `gcloud artifacts` command revealed gcloud was pinned to an old version.
So, updating the gcloud image to the latest, and correctly document that it has been pinned to a specific version
Currently golang-test Task is using tektoncd/cli repo to test the task
golang-test but that's too flaky so changing that to use another repo.
Signed-off-by: vinamra28 <vinjain@redhat.com>
Prior to this commit we were using Pipelines 0.28 for running e2e tests
in the Catalog.
This commit updates the pipelines version used during testing to 0.32.0,
which was released today.
After making this change one of the steps in an Orka Task is now failing
due to a naming conflict. This commit also renames the step to work
around the issue.
`upload-pypi` Task version 0.2 is failing during nightly tests and
reason for the failure was that the image digest was inaccessible.
Updated the image with the tag `v0.0.2`
Signed-off-by: vinamra28 <vinjain@redhat.com>
This changes the container registry where Argo CD image is pulled from
docker.io to quay.io (the project deprecated publishing on Docker Hub
since a few releases, and will stop publishing new images to there
soon). Also bumps the default version used by the task to the latest
stable release.
Signed-off-by: Jann Fischer <jfischer@redhat.com>
Since much time has passed since the Argo CD release v1.0.2 and meanwhile the
registry for official upstream containers has changed to quay.io, the version
0.1 of this task is being deprecated in favor of its new 0.2 version which
will adapt to more reasonable default settings.
Signed-off-by: Jann Fischer <jfischer@redhat.com>
The following version of kythe-go task contains the latest changes in order
to make it compatible with the latest kythe binary. Added a few
environment variables and mountPath which contains go.mod
Signed-off-by: vinamra28 <vinjain@redhat.com>
Kythe-go version 0.1 is being deprecated as it's incompatible with
latest versions of golang and the tests are also failing.
Signed-off-by: vinamra28 <vinjain@redhat.com>
Prior to this commit an example in the readme for gcs-download
referenced a Task that didn't exist.
This commit updates the broken taskRef to point to the correctly
named Task.
The default image for the github-set-status is more
than 800MB. The python code actually run in this task
is small and used only the stdlib. A smaller image
would works just as well.
The new default is python-alpine (45MB), which is the
smallest python image possible. It is now configurable.
Looks like the `context` param is never used in 0.2 which fails builds that don't have the golang sources at the workspace root. Seems like a regression from 0.1.
Specification of Docker config location allows to point jib tool to the
Docker config file with registry auth information, provided by Tekton
via
https://github.com/tektoncd/pipeline/blob/main/docs/auth.md#configuring-docker-authentication-for-docker .
Without this fix jib is not able to find credentialss for private registries or
registries will limited pulls and build fails.
Fix is provided for all 3 existing versions of the task.
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
The recipients of the email are extracted from a variable using the
split() function on a blank space (' '). If there are additional blanks,
either before, after or in the middle of the receivers_email variable the
sendmail function will cause an exception. This patch makes sure that blanks
won't cause the exception.
