Hi,
im not sure if i get you correctly, but have you tried a parametrized build
to set a variable with your server and
use this later ? Because the help description includes :
"The Build requires user input (this would be your server) which will be
available during the build process."
If i cre
This is all nice, but the envinject plugin seems to be the only way to pass
parameters between jobs. And, apparently, post build actions, even though
they are configured as part of one job, are considered as separate jobs and
therefore cannot use the parameters of the original job. The envinject
Generally, a plugin that has more releases than a core component, this
does not sound too bad for me.
Am Dienstag, den 01.01.2013, 10:59 +0100 schrieb domi
:
The idea of the envinject plugin is really nice, but It sounds more
and more like not a good idea to use it - it seems very unstable a
The idea of the envinject plugin is really nice, but It sounds more and more
like not a good idea to use it - it seems very unstable and soon it will have
more releases then jenkins core… :(
On 01.01.2013, at 01:32, "glsilver...@pssd.com" wrote:
> Correction from my original post: The first p
Correction from my original post: The first part of the stack trace
returned in the console is:
if (SERVER==null){return null;}
if ("qa".equals(SERVER)){ def map = [MYSERVER: "dsiqa2-fed17"] ; return map }
if ("newprod1".equals(SERVER)){ def map = [MYSERVER: "newprod1"] ; return map }
if ("newpr
I configured my Jenkins (v:1.492) maven job for parameterized builds and to
use the following evaluated groovy script:
if (SERVER==null){return null;}
if ("qa".equals(SERVER)){ def map = [MYSERVER: "dsiqa2-fed17"] ; return map
}
if ("newprod1".equals(SERVER)){ def map = [MYSERVER: "newprod1"] ;
