Given a large use of parallel is to run chunks of steps on different agents, it may make sense to allow agent to be configured in a parallel branch vs only at the parent stage level.

      Currently parallel lives at the steps level, so this likely could be a disruptive change (maybe not).

      Currently to use distributed builds in parallel vs sequential means dropping in to using the node syntax (and excludes usage of things like docker inside), which is a bit of a disjointed experience.

          [JENKINS-41198] Per parallel branch agent configuration

          Andrew Bayer added a comment -

          This is covered implicitly by JENKINS-41334

          Andrew Bayer added a comment - This is covered implicitly by JENKINS-41334

          Liam Newman added a comment -

          Bulk closing resolved issues.

          Liam Newman added a comment - Bulk closing resolved issues.

            abayer Andrew Bayer
            michaelneale Michael Neale
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: