Jochen Hinrichsen (2015-03-18 12:08):
Dear group,
we want to follow the same rules for Jenkins jobs that our software
itself must confirm to: development in test, testing in staging, and
the official version in a production environment. Copy and paste will
always work, but i'm too lazy to do that for the 200+ jobs. Maybe
something more git-ish?
From a first glance, i can see that everything credential related is
different in the underlying xml configuration files. So a plain 1:1
copy of a job's external xml representation will not work.
If you have 3 Jenkins installations that are identical (i.e. two of them
have jenkins-data folder copied at first) then you could simply copy
config.xml between them. I'm not sure which of the files is used for
credentials encryption but my wild guess is that its the `secret.key`
file ;-).
Regards,
Nux.
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/550962A5.9050902%40mol.com.pl.
For more options, visit https://groups.google.com/d/optout.
