|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
I solved this by using a Git poll job polling every Git branch. This poll job then starts the long build pipeline and every job in this pipeline has a parameter for the branch. So I can achieve to use the same job for different branches.
The main disadvantage is, that a green Jenkins does not mean, all branches are green. Only the last build of some branch is green. This does not get better when using the dynamic axis plugin for the branches. You still can not see, if all branches are green.
So we have a last job in the pipeline, that collects all test results, build results from the complete pipeline and publishes that. Developers have then only to look into the builds of this last job to see, if some branch is green or not.
Having this all in a matrix view would be much more convenient. And furthermore this matrix should be variable somehow, so developers can create feature branches and those are tested automatically, too.