Hi, In my setup, the master does not execute the jobs. I have slaves with label corresponding to the OS, and other labels (for example, some related to tools that are installed). Also a "build" and "test" label.
Here is the matrix job configuration, 2 axis : - one "user defined axis", with several values, were a new value was added and caused problems. - one "slave axis", using labels. Only the "build" label is used. It is displayed as a one axis matrix as there only one choice for the second axis. Several slave have the label "build". So the child job will run in parallel on several nodes. On child job will not always execute on the same machine. Some days ago, I faced the same issue on a "user defined axis" matrix job where I just added the build label axis, The job has two configuration that are slave specific. On child job will always execute on the same node. The issue is not only when adding some values to a user defined axis. At some point, Jenkins wrongly uses the old job configuration. The good thing is that the missing build that had disappeared few hours after the build is back. I can everything in Jenkins. Some new builds have been performed with the new user defined axis label, and they are all visible. That means nothing is lost.
