Since with recent version of pipelines, affinity-assistant is enabled by
default and 2pvc cannot be bound to a pipeline at the same time hence
the task was failing
Remove the binding of optional workspace
few Tasks still uses PipelineResources which is no longer available
in latest version of pipelines hence marking them as deprecated
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
E2E tests were running an older version of pipelines ie v0.45.0.
Bumping it to use the latest version v0.51.0 so that current tasks in
catalog can be tested against latest version
Also remove pipelineresources check while doing installation of latest
version of pipelines
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
With git-clone version 0.8 and onwards, it started running as non-root
and GKE clusters were having some issues, so, we temporarily moved all
tasks to use git-clone version 0.7. Ref: https://github.com/tektoncd/catalog/pull/1079
Since we have now moved to kind clusters in our CI, this issue is now
resolved and thus moving all tasks to use latest version of git-clone
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
The previous tag, quay.io/skopeo/stable:v1.9.0, no longer exists. This
commit updates the image reference to use the `v1` floating tag.
Signed-off-by: Luiz Carvalho <lucarval@redhat.com>
This will bump jib-maven to 0.5
to handle the case where permission to
add certs to javacacerts is no there
we just create a new store with default certs and
add provided certs to that and use that cert
in mvn command
later delete the store on exit
Some tasks were referencing absolute paths for `results`. It is recommended
to use variable replacement syntax in the API spec. This PR migrates the
absolute paths for results to variable syntax notation.
As of now blue-green-deployment task assumes the namespace to be the
current namespace in which pipeline is running but everytime this might
not be the case. Added an extra parameter, `NAMESPACE` which user needs
to supply as the parameter in which the existing deployment and service
are present.
Also added an optional parameter `IMAGE` in order to improve the
flexibility for the user
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
While consuming the result `IMAGE_URL` produced by buildah task, a new
line character '\n' was getting appended and the same was causing issues
which using the task.
- Added `-n` flag with echo in order to remove the newline character
- Modified the tests for the same
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
Since @chmouel stepped down from maintaining catalog repository, he was
missing from Alumni, hence adding him there 🙂
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
when trying to cleandir, there could be some non owner files in there
(ie: lost+found)
let's not fail when failed to clean.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
See
https://github.blog/2023-01-17-git-security-vulnerabilities-announced-2/
for more details.
Because this effectively bumps the Git version used from v2.26.2 to
v2.39.0, this change also fixes 59 HIGH and 12 CRITICAL vulnerabilities
reported since this image was last updated.
This changes the default base image for git-cli and git-rebase to match the same base image for
[Pipeline
git-init](9d3942176f/.ko.yaml (L5)).
This does not update:
- git-clone | this is dependent on git-init (which is yet to be updated)
- git-version | this is based on dotnet sdk(?) so I have no idea how to
safely update this.
