Figured it out and deleted the original posts because they were effectively noise in the Google Groups. It was developer error. I was looking at a test input that would've generated more branches than free matching slaves, but mistakenly rebuilding my job with another test input where threads < available matching slaves.
When I fed it the "threads > slaves" input, parallel worked as expected: 5 concurrent threads, then 5 more, etc. until all branches in the map were executed. Thanks, On Tuesday, November 10, 2015 at 6:41:21 AM UTC-8, Jesse Glick wrote: > > On Mon, Nov 9, 2015 at 6:56 PM, Brian Ray <[email protected] > <javascript:>> wrote: > > [Crossposting from Jenkins Users because I have not been lucky there > with > > workflow questions.] > > This is a developer list. Your message is somewhere between a user > question and a bug report. If a user question, use the user’s list, or > the StackOverflow tag `jenkins-workflow`. > > > Is this a bug? > > Sounds like a bug. If you can reproduce from scratch in a clean > environment, please file it in JIRA. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/94bd7d41-3d3e-4261-89b4-315964718526%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
