|
||||||||
|
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.
Yes, since my last round looking at this topic I have also switched to the one-job-per-branch camp. This is what is most natural considering job status - different branches may have very little to do with each other and their statuses shouldn't be mixed up.
But the topic in this ticket is still very relevant and might be appropriate to address in the generic Jenkins code. Either an offical new "super job" entity that can control automatic creation of other jobs, or some simple "clone this job for all branches" setting on ordinary jobs. Then SCM plugins would be required to report the active branches, which could be done at the same time as checking for new checkins.