[JIRA] (JENKINS-15864) multi-configuration project ignores slave setting

[osmith@sysmocom.de (JIRA)]

Oliver Smith commented on JENKINS-15864

Re: multi-configuration project ignores slave setting This problem is happening with 2.190.1. We have a lot of jobs where the slave axis is set to a specific label. Jenkins always runs these jobs on build slaves, that are configured for the label. Except for one job, where the slave axis is getting ignored and it is always running on one specific node that does not have this label. The jobs are generated from this jenkins-job-builder config: https://git.osmocom.org/osmo-ci/tree/jobs/master-builds.yml?id=a7fcf3218d036d644285bc857309bf84c06f44a5#n10 I have also tried the following (directly in the jenkins web UI), but still jenkins is ignoring the setting and runs the job on the same, wrong node: delete the nodes axis and add it again set a specific node instead of the label delete the workspace Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)