https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md includes a section on "Creating Multiple Threads". It seems like that might be one way to accomplish the permutation of models and variants that you need. I think you would define the values of the models and variants, then loop over those values.
Mark Waite On Thursday, June 30, 2016 at 1:02:18 AM UTC-6, Rick Liu wrote: > > I'm planing to migrate Jenkins1 multi-configuration (matrix) job to > Jenkins2 pipeline (-as-Code) approaches, > but it seems the pipeline job and multi-branch pipeline job don't support > multi-configuration (matrix) job directly. > > What's the best practice to achieve this? > > Assume my project has 100+ different models with some variants (debug, > release, etc) to build, > and the only major difference among the build steps is > the first "Configure" step: > eg. > Configure --model $MODEL_NAME --variant $VARIANT > > In Jenkins1, > I'm using multi-configuration (matrix) with 2 axis - MODEL_NAME and > VARIANT to define the build. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0a0e94a0-8117-42fd-b41e-b5e115a13c75%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
