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

In multi-configuration projects where specific slaves have been selected, the top build is still performed on any slave

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • matrix-project-plugin
    • None
    • Unix

      If a multi-configuration project is configured, and it is set to run on certain slaves, the top build (the build checking out files and triggering the different configuration builds) is still run on any slave.

      For example, I have a label for the WINDOWS2008-servers in our environment. I have specified two different axis in a multi-configuration project, one for Configuration (two text values, Debug and Release) and one for Platforms (which is connected to the Slaves section with only the label WINDOWS2008 selected).

      When I trigger the build, the top build is executed on SRVLINUX01, one of our Linux build servers.

      Is this by design? Did I miss something? Hope the label component "matrix" makes sense, didn't find one for multi-configuration projects..

            kohsuke Kohsuke Kawaguchi
            jeinor Jonas Oscarsson
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: