[release-1.11] Autobuild on tag push #5945
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this aids with switching branches between master / release-1.11 Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
…hen tag pushed After a GCB trigger is configured, this configuration file will enable cert-manager releases to automatically be built when a new tag is pushed. This has been tested on a fork and confirmed to work. Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
|
This will help us to more easily release patch versions of 1.11. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: inteon, SgtCoDFish The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Motivation
#5940 backported to release-1.11 as discussed.
Also includes a QoL gitignore fix when switching between branches with workspaces on.
NOTE: This PR also implies a change in the build image used for releases of 1.11. We originally used this image and we change it here.
This is intentional.
eu.gcr.io/jetstack-build-infra-images/bazelbuild:20220629-ee75d11-4.2.1has many vulnerabilities including critical severity vulns. Someone attacking the release process using those vulns doesn't seem particularly likely, but it does seem worth updating here. Since make-dind is much more slim than bazelbuild, it seems worth using that to reduce attack surface.Kind
/kind feature
Release Note