Epic
Major We should offer a way to some people to get access to Essentials logging, so that they can understand usage patterns, issues, and improve them.
Acceptance criteria:
- Some developers, who have been marked as allowed to, should be able to access Essentials error logging received from running instances
- Those developers shall see only the Essentials logging, not all logs from Jenkins Infrastructure.
Technical insights
- LDAP is used behind the scene, so rtyler says we should be able to restrict/offer access leveraging it.
cc olblak
- is blocking
-
JENKINS-53419 Demo Jenkins Evergreen successfully at DevOps World Jenkins World in SF
-
- Resolved
-
[JENKINS-51299] Design a way to provide access to Essentials logs to some Jenkins developers
| Rank | New: Ranked higher |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
| Resolution | Original: Fixed [ 1 ] | |
| Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
| Status | Original: Reopened [ 4 ] | New: Open [ 1 ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Link | New: This issue is blocked by INFRA-1643 [ INFRA-1643 ] |
TBD whether we have a dedicated team of developers monitoring new errors and explicitly notifying those responsible; or whether there is a larger pool of “Essentials” developers with access to all the errors who would just be paying the most attention to those introduced by changes they had themselves made.