![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
22/May/14 10:14 AM
|
|
Description:
|
While Jenkins automatically downloads dependencies of plugins, it doesn't tell you when you have configured an invalid plugin configuration by disabling plugins: Features simply don't work.
Ideas:
New Administrative Monitor:
- Tell users about mandatory plugin dependencies that are missing or disabled
- Tell user when implied (pre core extraction) dependencies are missing or disabled
Enhance plugin descriptions to state dependencies, maybe color-code when they're missing or disabled.
Show a confirmation dialog before disabling a plugin when a user clicks the check box.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Daniel Beck
|
|
|
|
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.
