Feature request: multiple prefedined node-filters for Jobs
Reported by Robert Krombholz | January 23rd, 2011 @ 07:18 AM
Job creators should be able to map jobs to a predefined set of
saved filters.
Job user should than be able to pick a node-set from the list
before running the job.
This avoids having to copy one and the same job when you want to provide it for multiple environments/tiers.
Comments and changes to this ticket
-
Deleted User January 27th, 2011 @ 10:39 AM
- Tag set to “filters, nodeset, tags”
-
Alex-SF March 21st, 2011 @ 08:07 AM
- Assigned user set to “Alex-SF”
-
Anil A. Pal June 13th, 2011 @ 10:03 AM
+1 on this - being able to compose elements (like filters/nodesets and jobs) is much more powerful than binding them together, and avoids the maintenance problems of having to copy/clone (and then separately maintain) jobs that differ only in the set of nodes they are to run on.
-
Alex-SF July 9th, 2011 @ 01:45 PM
- Tag changed from “filters, nodeset, tags” to “feature request, filters, nodeset, tags”
-
Greg Schueler June 22nd, 2012 @ 10:56 AM
- State changed from “new” to “duplicate”
marking as dupe of #484
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues
People watching this ticket
Alex-SF
Greg Schueler
Robert Krombholz
Referenced by
-
484
Decouple Jobs from Workflows and Nodesets
Similar issues/requests: #70, #99, #185, #413, #414, #419...