-
Notifications
You must be signed in to change notification settings - Fork 32
Update configuration for the next cert-manager release 1.7 #605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
869d8e4
Run the pre-submit jobs against master and release-1.7
wallrj 54906a1
Run release-next periodic jobs against release-1.7
wallrj 839c61e
Run release-previous pre-submits and periodics against release-1.6
wallrj e8c0410
Configure milestone_applier for cert-manager current 1.6 and next 1.7…
wallrj bfbd4da
Sync release-previous job manifests with those in current and release…
wallrj 6e3414c
Fix inaccurate comment
wallrj 2b9b992
Sync the master periodics jobs with release-next jobs
wallrj File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion/question: I understand why this has been changed to
release-1.7, and I'd be fine with it staying this way... but for at least the next few weeks, am I correct that these tests aren't going to do anything useful in practice, because we won't be updating the release-1.7 branch?We could just comment out this whole config file basically until we do our first alpha for 1.7 and we'd lose nothing, I think. Periodics run against master do the "release-next" job until we create our first alpha.
(We've talked about wanting to do alphas more often, but we're not there yet and I'm thinking we could save some resources on our test cluster here)
Am I missing something? Could we, for now, not do any of these tests, or else maybe only run them every 2 days or every week rather than every 2 hours?
(I fully accept that this is a tangent to your PR here, and if you'd rather not have this discussion in this PR, then fair enough!)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. The release-1.7 branch will only ever be identical to, or behind master, so it's pointless to run these tests right now....but it's what we've always done so I propose not changing that in this PR.
We could create another PR to disable them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Totally reasonable to leave it for a separate PR, yeah. I might raise that PR after this merges 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I think in the past we have not created the release branch until we actually want to cut a release (i.e. just before the first alpha)