![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
01/Mar/15 2:45 AM
|
|
Description:
|
The typical system administrator, to urgently recover from a problem, will need to use local system commands to disable plugins indicated a problem in the Jenkins logs.
The first step is to include a "README" in the install and/or plugin directories. This readme file may be as simple as to link to the Jenkins online documentation describing the file structure and configurations.
Secondly, there should be clear documentation on the "manual" backup/restore/disabling plugins and their configurations.
Lastly, if it is not currently possible to disable a plugin via the command line and/or config update a process should be added to Jenkins to do so.
See thread https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFuG9t_F4zL%3D7ncg53XdZG9dZD-GdWQ1dtTN53DrKjm8g%40mail.gmail.com
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Jason Pyeron
|
|
|
|
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.
