That won't work because tasks you launch like this are being launched
directly, forked from the GoCD agent process. When you do this you're
setting the env vars for all processes that are launched from this process,
but not changing the agent process env itself. If this were allowed, it'd
create ch
Hi Jason:
For testing purposes I have created a single job pipeline:
[image: Captura de pantalla 2024-07-08 174021.png]
with this single environment variable:
[image: Captura de pantalla 2024-07-08 174219.png]
and this is the log I get when I run the pipeline:
[image: Captura de pantalla 2024-07
Hi Pablo,
Why do you feel that the PATH variable is not being honoured? You provide
two examples of details that suggest that it _should_ be working, but
assert that is not. What behaviour are you seeing that gives you that
impression?
With that said, I'm not sure that overriding the PATH is t
Hi,
I have configured a PATH environment variable in my pipeline,
I see an "overriding environment variable 'PATH' with value
'/usr/lib/jvm/java-11-openjdk:/usr/bin'" line in the logs, I even can see
the new value of PATH in an "printenv" task.
However, this value doesn't seems to be honoured a
