[6.6] Allow Jenkins to parse the release Jenkinsfile before cancelling non-release triggers #9617
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
…release triggers This way, we can update parameters/options and have Jenkins take them into account for the next build upon branch indexing or push, even though we don't release on branch indexing or push.
yrodiere
changed the title
beikov
approved these changes
Jan 14, 2025
yrodiere
added a commit
to yrodiere/hibernate-orm
that referenced
this pull request
Jan 15, 2025
…ing non-release triggers" This reverts commit ffecd7d. This reverts PR hibernate#9617 See hibernate#9571 (comment)
yrodiere
added a commit
that referenced
this pull request
Jan 15, 2025
…ing non-release triggers" This reverts commit ffecd7d. This reverts PR #9617 See #9571 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Backport of #9571 to 6.6
@beikov I was thinking we could merge this to 6.6 first, because on 6.6 it wouldn't be a complete disaster if my build conditions don't work and a release was triggered by mistake. Works for you?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.