|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Not sure this is a bug. Still, workaround is present, so reducing priority: Implement SaveableListener.onChange.
It seems to be a bug to me, the web interface and the REST API behave completely differently. The issue at hand is that changes made via the web interface triggers ItemListener events based on fields that have been changed. On the other hand, the REST API is just a way to upload a new config file, so it uses the SaveableListener which is rather dumb and fire an event which has the whole new XML file. Ie SaveableListener is a gross generalization while ItemListener is thiner.
Would it make sense to have the REST API to fire the ItemListener events as well? It might not be doable though since the only data available is the whole config file and I think the events need finer informations (such as a Label object, not a whole config file). Another way would be to have the SaveableListener events build in core to inject the new conf to the code that handles configuration changes for the web interface, thus reusing all the existing logic that ends up triggering ItemListener events.
To say it otherwise: I would expect uploading a config file to behave exactly the same as doing a change via the web interface form.