Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41198

Per parallel branch agent configuration

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            michaelneale Michael Neale created issue -
            michaelneale Michael Neale made changes -
            Field Original Value New Value
            Summary per parallel agent configuration Per parallel branch agent configuration
            Hide
            abayer Andrew Bayer added a comment -

            This is covered implicitly by JENKINS-41334

            Show
            abayer Andrew Bayer added a comment - This is covered implicitly by JENKINS-41334
            abayer Andrew Bayer made changes -
            Link This issue duplicates JENKINS-41334 [ JENKINS-41334 ]
            abayer Andrew Bayer made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Duplicate [ 3 ]

              People

              • Assignee:
                abayer Andrew Bayer
                Reporter:
                michaelneale Michael Neale
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: