#99 new

Jobref calls should support overriding node filter params

Reported by Alex-SF | November 29th, 2010 @ 08:45 AM

It is sometimes required for a coordination job to call subordinate jobs overriding them with its node filter and dispatch flags. This is needed because each job must be defined with filter expressions and dispatch flags of its own.

A coordination job must be able to override these like is possible with the run command arguments. Eg

 run ‐I tags=dev ‐X os‐family=windows ‐C 2 ‐K ‐j ’test/Job1’ -- -optionA valA

The jobref flag might support this syntax, too.

Three hypothetical strawman examples illustrate the theme:

Ex#1) Overload arg line attribute using the double dash as delimiter:

 <jobref group="test" name="Job1"/>            
     <arg line="‐I tags=dev ‐X os‐family=windows ‐C 2 ‐K -- -optionA valA"/>                                            

Ex#2) Allow nodefilters and dispatch tags as nested elements:

<jobref group="test" name="Job1"/>            
    <arg line="-optionA valA"/>    
    <nodefilters excludeprecedence="true">                                                               

Ex#3) Provide a shorthand tag that implicitly overrides the nodefilters and
dispatch configuration for the subordinate job:

<jobref group="test" name="Job1"/>            
     <override nodefilters="true" dispatch="true"/>
     <arg line="-optionA valA"/>                                            

Comments and changes to this ticket

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