Details
-
Type:
Epic
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: core, diagnostics-plugin, monitoring-plugin, support-core-plugin
-
Labels:None
-
Epic Name:Improve Jenkins Supportability
-
Similar Issues:
Description
Problem statement
As an administrator, I want to know where to look at when I have a specific issue.
Examples
- My server is unresponsive, slow, etc.
- I see intermittent connectivity issues, agents get disconnected
- Sometimes authentication does not work, is slow...
- …
Better Information Accessibility
- Write blog entry to make some noise about the plugin(s) and docs in this area?
- Make troubleshooting-related plugins more well-know (or not?)
- Initiate a troubleshooting part under jenkins.io
- Refactor/move https://wiki.jenkins.io/display/JENKINS/Troubleshooting there
- There are already some troubleshooting-related parts in the user handbook, but no dedicated “Troubleshooting” AFAWCT.
- Add a new category “troubleshooting” for those plugins? To be presented/selectable through the plugins’ site left menu checkboxes?
(Context: this issue was discussed during the pre-FOSDEM Jenkins meetup that happened on Friday 2nd February 2018, mainly with Dario, Félix Belzunce Arcos & Baptiste Mathus. Originally in that document).
Attachments
Activity
For now, not yet. But maybe some things will be made also more actionable/driven by Essentials, not sure of anything yet. Maybe we could automate some bundle reporting in case things get wrong, or so, overall help end users get things fixed (automatically as much as possible being the goal, but well).
cc R. Tyler Croy
Baptiste Mathus Adrien Lecharpentier any plans regarding this EPIC?
Without tickets it does not have much future