hey, thanks guys! you're absolutely right. I made a file, wrote the
information to that file, then instructed a later job to read that file
On Friday, April 16, 2021 at 7:58:03 AM UTC-5 Harry G. wrote:
> Yes, a file would be a valid way - still you have to get that file in this
> pipeline, e.g.
Yes, a file would be a valid way - still you have to get that file in this
pipeline, e.g. by copy artifacts plugin.
By far easier would be if you switch to scripted pipeline and run the
variable modification directly in this pipeline instead of a separate job.
Then you could get a file or simply
How about writing the value to a temporary file instead? A shell
script could use the file later on (in another stage) to set the
environment variable.
On Wed, Apr 14, 2021 at 9:01 PM webde...@gmail.com
wrote:
>
> hey, all!
>
> Here's what I would like to do:
>
> 1. in the pipeline itself, create
hey, all!
Here's what I would like to do:
1. in the pipeline itself, create an environment variable.
2. pass that environment variable to a job
3. that job will overwrite the environment variable's value at the top level
4. a later job will use this new value within its execution.
something like
