![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
20/Nov/13 4:37 PM
|
|
Description:
|
Jenkins has only one top level folder containing everything. Many third-party web applications have a top level distinction between application/configuration and user data. Take for example Sonatype Nexus. It has two main folders - "nexus-x.x.x" and "nexus_data".
More specifically, within Jenkins the file config.xml contains items that could be considered user data (most notably view definitions) as well as application-level configuration (pretty much everything else). This becomes problematic when attempting to manage a Jenkins instance programmatically (e.g. via Puppet). User changes must be added upstream before applying a configuration update.
|
|
Environment:
|
Centos 5.9
|
|
Fix Versions:
|
current |
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
nw
|
|
|
|
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.
