Handling In-process Script Approval

[jacek.sni...@agilone.com]

My jobs use parameters created by Groovy scripts via Extended Choice parameters and Active Choices Parameter.

These scripts change, as they return list of available builds.

As a result, every time I regenerate the jobs with JobDSL, I have to manually approve a bunch of Groovy scripts.

For now I just have a Groovy script job that is hooked up as a post build step and it approves all scripts but this is not maintainable for me in the long run.

1. Active Choices Parameter has a 'Run in sandbox' mode but JobDSL doesn't provide a way to enable it. I could resort to 'config' node but would prefer something less messy.

2. Extended Choice doesn't even provide that parameter, so what can I do in that case?

Thanks for the help.

[jacek.sni...@agilone.com]

Solved.

I moved the Groovy script to Scriptler and converted all jobs to use Active Parameter plugin with this code:

parameters {

        activeChoiceParam('branchToBuild') {

          description('Select a release branch to build from.')

          choiceType('SINGLE_SELECT')

          scriptlerScript("getBranches.groovy") {

            parameter("repoName", "myRepo")

          }

        }

      }

[Stefano Salvatori]

Hi

Do you have the code for this "automatic" approval ? i'm trying to do the same using for some job's seeders and also some pipelines

S.

[jacek.sni...@agilone.com]

Hi, Stefano. Sure, this is the Groovy step I used. You need to put it in the 'Execute system Groovy script' build step:

import jenkins.model.Jenkins

def scriptApproval = Jenkins.instance.getExtensionList('org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval')[0]

def hashesToApprove = scriptApproval.pendingScripts.collect{ it.getHash() }

hashesToApprove.each { 

  scriptApproval.approveScript(it)

}