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.
Earlier Billy's repo was being used in which the latest pipelines
version was getting installed. Changing to Vinamra's fork as the version
is pinned.
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
The current CNB_PLATFORM_API version 0.4 is a bit old and does not support SBOM format, etc.
This change bumps up the version to 0.9 for buildpack task.
E2E tests are failing for the reason
```
ERROR: (gcloud.beta.container.clusters.create) ResponseError: code=400,
message=Creation of node pools using node images based on Docker
container runtimes is not supported in GKE v1.23. This is to prepare
for the removal of Dockershim in Kubernetes v1.24. We recommend that
you migrate to image types based on Containerd (examples). For more
information, contact Cloud Support.
```
The changes have been made in plumbing directory to fix the same, hence
bumping.
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
We were doing first but when having a
WORKSPACE_BASIC_AUTH_DIRECTORY_BOUND we would erase the .gitconfig and
that safe variable would not be there anymore.
Do this only right before calling the git-init so we know the setting
would be applied.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
this updates goreleaser image to latest.
faced issue with cli release, and the image was last updated almost
10 months back.
Signed-off-by: Pradeep Kumar <pradkuma@redhat.com>
* Add backwards compatibility for previous version
* Update default image
* Ensure the task will now fail when a command exited with a
non-zero exit code. This was a bug in previous yq versions, see:
https://github.com/mikefarah/yq/issues/1062
* Add optional result
* Add default value for SCRIPT for backwards compatibility
* Handle empty SCRIPT param
