#413 new
Arthur Freyman

refrence job inheritance

Reported by Arthur Freyman | August 10th, 2011 @ 12:41 PM

When calling a reference job, there is no ability to pass dynamic filters to it, in effect having a type of inheritance or filter override.

In a scenario where you have a a job that executes on Nodes A,B,C, one at a time, the job will execute step one on NodeA, then the reference job will be called in step 2 which is going to execute on Nodes A,B,C (if that's the filter) and it's going to back to step 3 executing on NodeA. You should be able to pass a dynamic filter to to a reference job.

For example, a ${nodes.matched} or a ${node.current} dynamic variable that could be passed would resolve this issue. ${node.current} in particular I think would be more useful, specifically for a "Node-Oriented" workflows. The general scenario where this would be useful is where you have your scripts broken down into small jobs, which creates a lot of reusable components. This way you can create a "meta" job and target it to a set of nodes (tags), but execute sequentially.


No comments found

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.

New-ticket 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

Shared Ticket Bins

People watching this ticket

Referenced by