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

          Michael Neale created issue -
          Michael Neale made changes -
          Summary Original: per parallel agent configuration New: Per parallel branch agent configuration
          Andrew Bayer made changes -
          Link New: This issue duplicates JENKINS-41334 [ JENKINS-41334 ]
          Andrew Bayer made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Liam Newman made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

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

              Created:
              Updated:
              Resolved: