Ben Golding created JENKINS-13522:
-------------------------------------
Summary: Missing option "Restrict where this project can be run" /
always run on master
Key: JENKINS-13522
URL: https://issues.jenkins-ci.org/browse/JENKINS-13522
Project: Jenkins
Issue Type: Improvement
Components: build-flow
Environment: Build Flow 0.3
Red Hat Enterprise Linux 5.5 64 bit
Sun Java 1.6.0_20
Reporter: Ben Golding
Assignee: Nicolas De Loof
Priority: Minor
Add option to assign a slave by name or groups of slaves.
"Restrict where this project can be run" seems to be a standard option of
normal "free-style" jobs
Alternatively, perhaps better:
* A Flow is really only part of the job scheduling which is normally done by
the master. So it should run always on the master.
* Also the currently running Flow(s) should be shown on the LHS but not
associated with any particular slave. Rather in their own list.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
