|
||||||||
|
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.
@Nicolas: Your assumption is not correct. git SCM can detect changes in multiple branches during a single detect run. In our case this happens quite often. We are using the following branching model: http://nvie.com/posts/a-successful-git-branching-model/. This results in continuous commits in branches develop, release-something and hotfixes-something. Open-Xchange does this to develop features for the next release in branch develop, to harden the upcoming release in the release-something branch (bugfixing) and to maintain old releases (fixing of security issues e.g.).
This requires builds in different branches if those branches have changes. Additionally I want to view and monitor test results in all these branches without selecting a certain job run. To do this, we want to use the matrix feature.
Is this an exotic way of using git and Jenkins matrix feature?