![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
jyrkiput
|
|
Components:
|
gerrit, gerrit-trigger |
|
Created:
|
06/Jan/14 9:59 AM
|
|
Description:
|
In our setup, we sometimes need to push in a single commit changes which affect several folders. Each of these folders is connected to a different Gerrit Trigger-based job (using files filter). However, these jobs are downstream one of another in Jenkins, and use artifacts one of another. So it would be best if only the "upstream-est" job was triggered, and let Jenkins trigger the dependent downstream jobs via Jenkins dependency mechanisms. Therefore an additional parameter in the Gerrit Trigger plugin would be welcome, allowing "Forbidden Files" to be added to Project configuration. For example, if project B is downstream of project A, in project B, we could set as "forbidden files" the files of project A. This way, if a change affects a file in A AND B, A will get triggered, not B, thanks to the forbidden file option. Jenkins would have an internal downstream trigger of B after A is completed successfully.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
yannack bbbb
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
