[JIRA] [master-slave] (JENKINS-22494) Multiconfiguration project does not respect label restrictions

Wed, 24 Sep 2014 02:07:41 -0700

I know this issue is closed, but I would like to add my 2c. Perhaps we should consider re-opening this as a feature request. The jobs of a configuration project should 'inherit' the "Restrict where this project can be built" restrictions. These restrictions should apply in addition to any further restrictions in the matrix axes

This would have the following advantages:

  1. It's expected behavior. Only restricting the flyweight task surprises most people. (Why would I want to do that anyway?)
  2. Project-wide restrictions ('these jobs need a node with opengl') can be separated from the matrix axes (e.g. release/debug on linux/windows/osx).
  3. The single-value Label Axis work-around would be unnecessary. This work-around is also cumbersome: it makes passing artifacts between projects more 'brittle' since changing a restriction changes the artifact paths for all downstream projects.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to