|
||||||||
|
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.
This is on my list of things to implement since a while and I was thinking to implement it the way Jesse is talking about. So that means it would go into core/maven and not into a the config-file-provider. This would then also allow to define any implementation of the SettingsProviders as default.
Also I think it would make sense to define an option where the user/admin can force to reconfigure all existing jobs (or better to remove the current configured SettingsProvider) to fall back to the global default. This would allow an admin of a bigger installation to do an easy migration.
But maybe the later would also be OK if we just provide a groovy script (maybe in scriptler).