-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Minor
-
Component/s: core
We have a large number of views defined at our installation and we need to promote this view configuration to our other Jenkins environments. However, this information is stored within config.xml which is not a file that can easily be promoted without manual editing. It would be helpful to externalize the global view configuration into a different file so that it can be copied as-is to other Jenkins environments without editing.
- is related to
-
JENKINS-21006 Decouple the slave configuration from the global config.xml
-
- Resolved
-