The main problem is that it is not tied to a particular plugin. Each plugin you install contributes to the _javascript_ executed on the configuration page of each job. If any one plugin introduces an erroneous _javascript_ the whole configuration page stops working, leaving you gesssing which plugin could be the culprit.

The only real solution to this would be some kind of sandboxing of each plugin in an error handler that ensures that the rest of the configuration page still works, optimally telling the user which plugin broke so it can be fixed easier.

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/d/optout.

Reply via email to