jenkinsci / jenkinsci/script-security-plugin

[JENKINS-54226] Script not approved for use exception at the end of every build log - even for jobs with no groovy scripts

Open
#816 4 comments 0 reactions 0 assignees View on GitHub
component:script-security-plugin component:splunk-devops-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
76
Forks
181
Avg merge
14h 55m
Merged PRs (30d)
3

Description

org.jenkinsci.plugins.scriptsecurity.scripts.UnapprovedUsageException: script not yet approved for use*10:39:55* at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.using(ScriptApproval.java:466)10:39:55 at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval$using$0.call(Unknown Source)10:39:55 at com.splunk.splunkjenkins.UserActionDSL.perform(UserActionDSL.groovy:41)10:39:55 at com.splunk.splunkjenkins.listeners.LoggingRunListener.onCompleted(LoggingRunListener.java:85)10:39:55 at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211)10:39:55 at hudson.model.Run.execute(Run.java:1864)10:39:55 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)10:39:55 at hudson.model.ResourceController.execute(ResourceController.java:97)10:39:55 at hudson.model.Executor.run(Executor.java:429)

This exception is being thrown and logged at the end of every jenkins job invocation on our server, even jobs that have 0 groovy scripts in them.

Because the exception is thrown at the end of the job and appears as the last thing in the log, save for perhaps the line saying it has FAILED, this causes developers to assume that the exception is the cause of the build failure when it actually doesn't cause anything to break.

There are no unapproved script or method invocations in the script approval page. 

---
Originally reported by jaxley, imported from: Script not approved for use exception at the end of every build log - even for jobs with no groovy scripts


  • status: Open
  • priority: Minor
  • component(s): script-security-plugin, splunk-devops-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 7
  • imported: 2025-12-09

Raw content of original issue

org.jenkinsci.plugins.scriptsecurity.scripts.UnapprovedUsageException: script not yet approved for use*10:39:55* at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.using(ScriptApproval.java:466)10:39:55 at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval$using$0.call(Unknown Source)10:39:55 at com.splunk.splunkjenkins.UserActionDSL.perform(UserActionDSL.groovy:41)10:39:55 at com.splunk.splunkjenkins.listeners.LoggingRunListener.onCompleted(LoggingRunListener.java:85)10:39:55 at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211)10:39:55 at hudson.model.Run.execute(Run.java:1864)10:39:55 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)10:39:55 at hudson.model.ResourceController.execute(ResourceController.java:97)10:39:55 at hudson.model.Executor.run(Executor.java:429)
This exception is being thrown and logged at the end of every jenkins job invocation on our server, even jobs that have 0 groovy scripts in them.

Because the exception is thrown at the end of the job and appears as the last thing in the log, save for perhaps the line saying it has FAILED, this causes developers to assume that the exception is the cause of the build failure when it actually doesn't cause anything to break.

There are no unapproved script or method invocations in the script approval page. 

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.