|
||||||||
|
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.
Yes – that seems to work ok, but does not allow differentiation between the axes.
Our use case is to fan out from a build step to a set of deploy steps; deploy service X, service Y, service Z. Right now we just have a set of manually-duplicated, hand-edited jobs, but it'd be much cleaner if a multi-config build could be used, defining X, Y, Z as the values of the service_name axis. Being a continuous delivery pipeline, those deploy steps have a manual approval, so (for example) for a given build we could decide to push the button for "deploy X" and "deploy Z" only, hence building the top-level job (and allowing all sub-jobs to build as a result) wouldn't work for us.