Details
-
New Feature
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Duplicate
Description
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.
Attachments
Issue Links
- duplicates
-
JENKINS-41516 Groovy script console actions should be logged
-
- Open
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Remote Link | This issue links to "https://github.com/jenkinsci/jenkins/pull/6539 (Web Link)" [ 27746 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Labels | audit-logging core jenkins | 3.11-fixed audit-logging core jenkins |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Fixed but Unreleased [ 10203 ] |
Status | Fixed but Unreleased [ 10203 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Status | Reopened [ 4 ] | In Progress [ 3 ] |
Labels | 3.11-fixed audit-logging core jenkins | audit-logging core jenkins |
Link | This issue duplicates JENKINS-41516 [ JENKINS-41516 ] |
Resolution | Duplicate [ 3 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Pull Request: Feature/add script console listener by meiswjn · Pull Request #6539 · jenkinsci/jenkins (github.com)