${job.nodefilter} variable for passing Node filter to Job Reference

[ltamaster]

It could be very useful to have a job's context variable like ${job.nodefilter} in order to pass the node filter of a "overall" job to Jobs References Steps.

An user case example:

Job A => the overall Job
Job B is a step of Job A
Job C is a step of Job B
I would like to pass the node filter from Job A to Job B and Job C

For example passing the node filter to the Job References like:

[puremourning]

Isn't it simpler to just to ${node.name}. Or am I missing something?

[pgressa]

Imho this is very similar to #2074

[gschueler]

@pgressa yes it is similar. I think adding ${job.nodefilter} will be a simple way to solve part of the problem. Your request to have a way to create subset of the filter is also useful

[steveblackmon]

+1. Propagating a node filter across all of the job references called is an obviously useful behavior that seems to still be lacking.

[Slm0n87]

+1 - specially for more complex worflows that feature would make the node-definition easier by inheriting the nodefilter.

[ltamaster]

This was added on 2.10.2
#2974