Added a "Forbidden Files" optional parameter to Gerrit Projects [FIXED JENKINS-21232] #121
Conversation
This file contains 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 forbidden file allows the project not to trigger if any forbidden file has been impacted. This is very useful in chained scenarios. For example, let's assume projectA upstream triggers projectB downstream. Then if a commit affects both A and B, you may (depending on configuration) want that A triggers and B wait for A to finish, and then trigger B. This would be the case in particular if B uses artifacts from A. Since A is triggering B anyways, no need for B to trigger. In that case, this commit allows you to define the files in "A" as forbidden to trigger a gerrit event in B. This means that such a commit affecting both projects A and B will only trigger A. B will be built as usual as a downstream element of A. Yet, a commit affecting only B will still trigger a build of B. This is a very specific use case, but in this use case, only this commit can satisfy the requirement. Amends: broken style-checks and forgotten test changes
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
rsandell
added a commit
that referenced
this pull request
Jan 15, 2014
Added a "Forbidden Files" optional parameter to Gerrit Projects [FIXED JENKINS-21232]
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.
This forbidden file allows the project not to trigger if any forbidden
file has been impacted. This is very useful in chained scenarios. For
example, let's assume projectA upstream triggers projectB downstream.
Then if a commit affects both A and B, you may (depending on
configuration) want that A triggers and B wait for A to finish, and then
trigger B. This would be the case in particular if B uses artifacts from
A. Since A is triggering B anyways, no need for B to trigger. In that
case, this commit allows you to define the files in "A" as forbidden to
trigger a gerrit event in B. This means that such a commit affecting
both projects A and B will only trigger A. B will be built as usual as a
downstream element of A. Yet, a commit affecting only B will still
trigger a build of B. This is a very specific use case, but in this use
case, only this commit can satisfy the requirement.
Amends: broken style-checks fixed and forgotten test changes added