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

multi-configuration project ignores slave setting

XMLWordPrintable

      After upgrading from 1.488 to 1.491 (could not test the others because of a bug with mercurial) one of our builds started to fail. It is a multi-config build with two axes, one of which is a workaround to get the "restrict where the project can be built" functionality which is not available for multi-config builds. It is a "Slaves" axis with only the Jenkins master node selected. However, the project always seems to be built on a windows node which doesn't even have mercurial installed.

          [JENKINS-15864] multi-configuration project ignores slave setting

          c089 created issue -

          c089 added a comment -

          It even uses the same slave all the time...

          c089 added a comment - It even uses the same slave all the time...
          rsandell made changes -
          Component/s Original: multi-slave-config [ 15928 ]

          rsandell added a comment -

          Nothing to do with the multi-slave-config plugin.

          rsandell added a comment - Nothing to do with the multi-slave-config plugin.
          rsandell made changes -
          Assignee Original: rsandell [ rsandell ]

          c089 added a comment -

          After I used "mark this node as temporarilly offline" on the windows slaves, the job successfully built on the master, but as soon as one was up, it's back on the windows node...

          c089 added a comment - After I used "mark this node as temporarilly offline" on the windows slaves, the job successfully built on the master, but as soon as one was up, it's back on the windows node...

          Peter Eisentraut added a comment -

          I can confirm this with Jenkins 1.558. I converted a job from a plain job to a multi-configuration job (making a new job and copying all the settings meticulously). The multi-configuration job appears to ignore the setting "Restrict where this project can be run" and always runs on the master node.

          Peter Eisentraut added a comment - I can confirm this with Jenkins 1.558. I converted a job from a plain job to a multi-configuration job (making a new job and copying all the settings meticulously). The multi-configuration job appears to ignore the setting "Restrict where this project can be run" and always runs on the master node.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 146666 ] New: JNJira + In-Review [ 176675 ]
          Oleg Nenashev made changes -
          Component/s New: matrix-project-plugin [ 18765 ]
          Component/s Original: remoting [ 15489 ]

          Oleg Nenashev added a comment -

          IIRC it works fine in newer versions. Fixed the JIRA component

          Oleg Nenashev added a comment - IIRC it works fine in newer versions. Fixed the JIRA component

            Unassigned Unassigned
            c089 c089
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: