After setting a Jenkins environment variable with the slave labels, and setting a dynamic axis variable builds are done on master instead of the remote slaves.

      What we want is to have this global environment variable containing all slave targets used for multiple projects and update only this variable when a new target needs to be added or removed for all projects.

      What are we doing wrong?

          [JENKINS-38200] building on master instead of remote slaves

          There are no comments yet on this issue.

            kohsuke Kohsuke Kawaguchi
            mezzano Tanguy Mezzano
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: