[Feature Request]: JOB_NOW passed on to chained jobs

[LyricalBernardin]

Is there an existing feature request for this?

• I have searched the existing issues

What is your feature request?

I a chained job is triggered, it runs under its own JOB_NOW env. Do you think it'd be helpful to use the same value of its predecessor?

Code of Conduct

• I agree to follow this project's Code of Conduct

[jhuckaby]

Hmm, I don't think this should be the default behavior.

I suggest passing the JOB_NOW as output data from the first job, which you can read in on the next job. Example using shell:

# in first job...
printf '{ "xy":1, "data": { "job_now": "%s" } }\n' "$JOB_NOW"

And then on the next job, the value comes in as data_job_now, but it can be reassigned back to JOB_NOW replacing the current one:

# in second job...
JOB_NOW=$data_job_now

Would this solve your issue?