![]() |
|
|
|
|
Change By:
|
Khai Do
(13/Dec/13 10:16 PM)
|
|
Description:
|
We have a large number of
views defined at
slaves configured to run on
our
multi-master jenkins
installation
and we need
.
We would like
to
promote this view configuration
to
our other Jenkins environments
do the following:
1
.
However, this information is stored within config
We have setup a multi-master jekins installation using the jenkins gearman-plugin
.
xml which is not
We would like to share the slave configurations across multiple masters.
2. We run our slaves on the cloud and have created
a
file that can easily be promoted without manual editing
separate application to automatically spin up slave machines and make them connect to the jenkins master
.
It
When new slaves are created/removed we
would
be helpful
like
to
externalize
update
the
jenkins slave configurations.
Since the jenkins
global
view
config.xml contains
configuration
into a different file so that
for master and slaves
it
can be copied as-
makes the above use cases difficult. My suggestion
is to
other Jenkins environments without editing
de-couple the two configurations
.
Maybe put the slave config in another file.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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.
