|
Hi All, I have maven project where i need to set environment
variable for that particular job. But i am not able to any textarea/textbox for
environment variables. It contains “Root Pom” and “Goals and
Options”. I do not want to use global environment variable settings. Any idea will be appreciated. Thanks Pawan |
|
Can't you use a parametrized plan for which you specify a, for
example, string parameter? That variable becomes an environment variable. Unless that's what you do not want to do, not sure what you mean by global environment variable, as in global to Jenkins or at OS level. |
|
I mean to say global environment variables settings in "Manage Jenkins" page.
I have environment property of DYNAMO_HOME which i need to change for each three projects. Isn't there any difference between setting environment variables and passing parameter to a mvn clean install. Thanks Pawan -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Scal Sent: Wednesday, April 20, 2011 5:16 PM To: Jenkins Users Subject: Re: Environment Variable for a particular maven job? Can't you use a parametrized plan for which you specify a, for example, string parameter? That variable becomes an environment variable. Unless that's what you do not want to do, not sure what you mean by global environment variable, as in global to Jenkins or at OS level. |
|
Global environment variables are suitable for ALL projects. You need
to customize environment variables according to projects. I suggest you look at. https://wiki.jenkins-ci.org/display/JENKINS/Setenv+Plugin This one is very good if you only need to customize couple of variables. https://wiki.jenkins-ci.org/display/JENKINS/Envfile+Plugin Use this if you already have your environment variables in source control file. On Thu, Apr 21, 2011 at 8:32 PM, Gandhi, Pawan <[hidden email]> wrote: > I mean to say global environment variables settings in "Manage Jenkins" page. > > I have environment property of DYNAMO_HOME which i need to change for each three projects. > > Isn't there any difference between setting environment variables and passing parameter to a mvn clean install. > > Thanks > Pawan > > -----Original Message----- > From: [hidden email] [mailto:[hidden email]] On Behalf Of Scal > Sent: Wednesday, April 20, 2011 5:16 PM > To: Jenkins Users > Subject: Re: Environment Variable for a particular maven job? > > Can't you use a parametrized plan for which you specify a, for > example, string parameter? That variable becomes an environment > variable. > Unless that's what you do not want to do, not sure what you mean by > global environment variable, as in global to Jenkins or at OS level. > -- Heinlein - Specialization is for Insects A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -Robert A. Heinlein |
| Powered by Nabble | See how NAML generates this page |
