[JIRA] (JENKINS-60419) Blocked classpaths are not shown on script approvals page

3 views
Skip to first unread message

dizeee@dizeee.ru (JIRA)

unread,
Dec 18, 2019, 6:34:10 AM12/18/19
to jenkinsc...@googlegroups.com
Aleksei Vesnin updated an issue
 
Jenkins / Bug JENKINS-60419
Blocked classpaths are not shown on script approvals page
Change By: Aleksei Vesnin
Summary: Blocked classpaths are not shown on script approvals page (workflow job)
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

dizeee@dizeee.ru (JIRA)

unread,
Dec 18, 2019, 6:36:05 AM12/18/19
to jenkinsc...@googlegroups.com
Aleksei Vesnin updated an issue
Groovy classpaths for Extended Choice Parameter in a workflow/pipeline job for `Groovy Script` are blocked with message `You have unapproved groovy scripts that need approval before they can be executed. Go to In-Process Script Approval page to approve your scripts.`, which is expected. But on the script approval page it says `No pending classpath entry approvals.`.

For
freestyle jobs `Groovy Script File` it kind of works with a groovy script file , I can approve or deny a classpath entries, but if multiple classpaths are defined and approved for a parameter, the parameter script doesn't see them. E. g. there are `src` and `resources` folders and class `src/io/domain/Config.groovy` which loads `resources/io/domain/config.yml`. When I only add `src` to the classpath it complains that it can't find `io/domain/config.yml` file, which is expected, but when both `src` and `resources` are added to the classpath (and both are approved), then the same script fails with `unable to resolve class io.domain.Config` exception, which is a bummer. And with Groo

These are probably two different classpath issues, please let me know if you need a separate ticket for the latter.

 

Jenkins version: 2.190.3

Extended Choice Parameter plugin version: 0.78

 
Reply all
Reply to author
Forward
0 new messages