Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default Option values are ignored when a jobs is referenced from another job.. #577

Closed
diranged opened this issue Oct 29, 2013 · 1 comment

Comments

@diranged
Copy link

When JobA calls SubJobB and does not pass in ALL of the options, any options that have Default values fail to be parsed at all. Instead, they act as if the option does not exist (ie .. "@option.DRY@" really looks like "@option.DRY@"!).

@gschueler
Copy link
Member

In scripts, missing option values are replaced with blank string (as of 1.6), however, note that Script File steps do not have an token substitution used.

I am seeing a behavior in 2.0 dev where option value that has not been set is not replaced with a blank string, so I will fix that.

However, (in 2.0) job references do get default values substituted for unset options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants