EnvInject also lets you write to a properties file in one build step
then inject that file for use in all subsequent build steps.
I see that your plugin may make it a bit more convenient to do so, but
it would be better to merge that functionality into EnvInject, rather
than publishing a separate plugin.
Regards,
Chris
On 26/05/15 15:25, Daniel Olausson wrote:
No that plugin let's you provide a file containing environment variables
that are then injected at build execution start.
My plugin provides the user with a file where he/she can store
environment variables across build steps.
On Tuesday, 26 May 2015 08:02:10 UTC+2, Dominik Bartholdi wrote:
The I guess its about the same as:
https://wiki.jenkins-ci.org/display/JENKINS/Envfile+Plugin
<https://wiki.jenkins-ci.org/display/JENKINS/Envfile+Plugin>
/Domi
On 25 May 2015, at 21:07, Daniel Olausson <[email protected]
<javascript:>> wrote:
Hi,
GitHub:
https://github.com/rednuht/retainenvironment
<https://github.com/rednuht/retainenvironment>
Description can be found at:
https://github.com/rednuht/retainenvironment/blob/master/README.md
<https://github.com/rednuht/retainenvironment/blob/master/README.md>
Shares some similarities with the EnvInject plugin but my plugin
doesn't require the user to use any additional build steps.
Br,
Daniel Olausson
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" 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/jenkinsci-dev/5564776A.2030005%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.
