|
||||||||
|
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/d/optout.
This seems to me a very odd behaviour.
They way we set up Jenkins is that anyone can queue a merge into the staging environment with their specific branch as the parameter. The build tests that the branch can be merged into staging, tests that all the tests still pass, and only then adds the branch to staging and redeploys it for human testing.
Parametrized workflows get merged as if there is no difference between them, and if I understand correctly, changing the stage name means the workflows will run in parallel. Neither option is viable in our setup.
Is there some way to make this work with workflows? What I want to do is coalesce the logic from multiple jobs into a workflow and parallelize the testing, so it won't take as long. Before noting this issue, the workflow plugin seemed like a very nice way to get this done.