Hi,
I noticed that Maven2/3 and free-style projects behave differently with
respect to environment variables. If my settings.xml contains:
<properties>
<gpg_passphrase>${env.gpg_passphrase}</gpg_passphrase>
</properties>
then Maven2/3 projects will generate an "alternate settings.xml file" with
the environment variable value inlined, and perform the Maven command with
-s <alternative settings>. When executing the exact same thing with
free-style projects, Maven does not inline the values or use -s
<alternative settings>.
Is there a way for me to get free-style projects to behave the same as
Maven2/3 projects? I'm invoking a release:perform which forks sub-processes
which do not inherit the environment variables so the gpg passphrase never
gets set. Invoking -s <alternative settings> in the parent process is an
ideal workaround. Any ideas how to get it working?
Thanks,
Gili
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
