|
||||||||
|
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.
Not sure if this is a different use case, but at least for us using maven we need the release to be performed on only one of the configurations in a multi-config project.
We use multi-config to run the tests in different environments (usually webdriver browsers), but only want to create a single release. The current approach would result in duplicate SCM tags, updates to poms, deployments of released versions to nexus, etc (if we didn't have tools in place to stop them)
Could an option be added to select a single config matrix to be used for release builds?