|
||||||||
|
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.
> The upgrade is automatic if you simply build your project after updating the plugin.
I know that and that cannot resolve the problem at all.
The problem is that, modifying the configuration before building breaks the configuration, and there is a case that a project administrator and a Jenkins administrator are different.
> there are various ways the storage could be upgraded automatically without requiring a build.
Do you plan to work that?
Or please let me know the outline of those ways, and I work it.
I think the difficulty is the case a project is not contained in ItemGroup other than Jenkins, and cannot be enumerated with Jenkins#getItems.
I have no idea about the proper way to visit all projects.