-
Improvement
-
Resolution: Fixed
-
Major
-
None
As I have define a settings / global settings for my infrastructure, I'd like all maven jobs to use it without users to manually configure in advanced section - they probably don't know about this.
ItemListener.onCreate could be used to enforce a maven setting/global setting that has been set to "apply by default"
- depends on
-
JENKINS-17858 <f:dropdownDescriptorSelector> does not allow defaulting to specifig instance
-
- Resolved
-
- is related to
-
JENKINS-16706 Configure provided settings.xml at the Maven plugin level, not at the Maven job level
-
- Open
-
[JENKINS-17723] mark maven settings / global settings as default for new jobs
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Link |
New:
This issue depends on |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Rather than hacking around with ItemListener (which may not work reliably when using REST, templates, etc.), better to have an instance-wide default which can be set in /configure and if necessary overridden for special jobs.