Hi David,
If the concern is keeping multiple jobs in sync, maybe the Template
Project Plugin would help:
https://wiki.jenkins-ci.org/display/JENKINS/Template+Project+Plugin. It
allows you to define one job that holds all the common settings, such as
SCM, build scripts, publishers, etc. and incorporate that into other jobs.
Eric
On 5/22/2013 4:59 PM, David Brossard wrote:
I have been trying to setup a single build job that will accept a
parameter to build for different environments ie Dev, Prod etc.
Obviously I also want these to deploy to different servers.
I can see how to use GIT to check out a different branch using
parameters but how then do I send these parameters in the names of
servers to publish over ssh, publish over ftp, publish over cifs etc?
We have server names similar to dev.mycompany.com and
prod.mycompany.com and I would like to send these to $ENV.mycompany.com.
The problem I have run into is that if I build a different Jenkins
jobs for our Dev and Prod servers, occasionally changes to the jobs do
not get replicated to every other one.
--
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.
--
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.
