building on master instead of remote slaves

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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?

            Assignee:
            Kohsuke Kawaguchi
            Reporter:
            Tanguy Mezzano
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: