using Job References, ${DATE} only gets expanded as option value in the top job. #2039

Closed
ltamaster opened this Issue Aug 31, 2016 · 1 comment

Projects

None yet

2 participants

@ltamaster
Contributor

Using the default value ${DATE} doesn't work when the job is part of a Job References.
It just works on the "father" Job, but it is not expanded on the job references.

The short term workaround is passing the top level option to job reference.

Example:

screenshot from 2016-08-31 18-19-48

screenshot from 2016-08-31 18-21-24

screenshot from 2016-08-31 18-25-26

@gschueler gschueler added the bug label Aug 31, 2016
@gschueler gschueler added this to the 2.6.10 milestone Aug 31, 2016
@gschueler
Contributor

Question: the ${DATE} is expanded with the execution's "dateStarted" timestamp. However the Job reference may not execute until later... Should the job reference's ${DATE} be the same as the "dateStarted" for the execution, or the exact time that the Job reference executes?

@gschueler gschueler self-assigned this Sep 2, 2016
@gschueler gschueler closed this in 1311233 Sep 6, 2016
@gschueler gschueler removed the in progress label Sep 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment