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 the best way to accomplish your objective. I think using the Java-specific variables like JAVA_HOME would be a cleaner way to handle your example case of multiple Java versions. I'm struggling to imagine a scenario where completely overriding the PATH isn't more trouble than its worth, though of course that doesn't mean that such a use case doesn't exist. Hope this helps. Cheers, Jason Smyth On Monday 8 July 2024 at 08:53:41 UTC-4 Pablo León wrote: > 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 as a search path! > > What is the recommend way to change the search path in go-cd? > > I know I can change this in the > /usr/share/go-agent/wrapper-config/wrapper-properties.conf > file, but what if I need a different paths for each job? (for example for > different java versions) > > Cheers! > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/dd726fae-4921-4550-869d-0f2169c366can%40googlegroups.com.
