-
New Feature
-
Resolution: Duplicate
-
Minor
The script console allows running arbitrary Groovy scripts on the Jenkins instance. While it can only be used by admins, it may still be desired to track its usage. Motivations to track it may be:
- Disaster Analysis (after running a destructive script)
- Audit requirements (Legal / Regulatory)
- Transparency
An extendable listener that is triggered during the script execution would be light-weight and flexible towards user's requirements.
- duplicates
-
JENKINS-41516 Groovy script console actions should be logged
-
- Closed
-
- links to
[JENKINS-68404] Add listener for script console to allow tracking its usage
Jan
created issue -
Alexander Brandes
made changes -
| Remote Link | New: This issue links to "https://github.com/jenkinsci/jenkins/pull/6539 (Web Link)" [ 27746 ] |
Alexander Brandes
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Alexander Brandes
made changes -
| Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
| Labels | Original: audit-logging core jenkins | New: 3.11-fixed audit-logging core jenkins |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Review [ 10005 ] | New: Fixed but Unreleased [ 10203 ] |
| Status | Original: Fixed but Unreleased [ 10203 ] | New: Resolved [ 5 ] |
| Resolution | Original: Fixed [ 1 ] | |
| Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
| Status | Original: Reopened [ 4 ] | New: In Progress [ 3 ] |
| Labels | Original: 3.11-fixed audit-logging core jenkins | New: audit-logging core jenkins |
| Link |
New:
This issue duplicates |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |