Troubleshooting requirements for jenkins jobs
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| UTAH |
New
|
Undecided
|
Unassigned | ||
Bug Description
When I have to troubleshoot a problem in a jenkins job outside our team I see
any of:
- Logs aren't available (in particular rsyslog log files)
- Logs are available, but just for the previous run (utah log files are stored,
but not archived as artifacts)
- It's difficult to troubleshoot the problem without that information
I'd like to address this issue from different points of view:
- Document what we need to troubleshoot a problem in a jenkins job that has
failed.
- Document how to configure a jenkins job to get what we need.
- Update code to make it easy to do it (the way we do it know with
UTAH_CONFIG_DIR isn't that easy).
Once we have this, it should be easy for us to point people to the
troubleshooting documentation and avoid spending time on figuring out what
happened when we are not provided with the information that we need.
