Details
-
Type:
Improvement
-
Status: In Review (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: pipeline-stage-step-plugin
-
Environment:Jenkins ver. 2.138.2
-
Similar Issues:
Description
I try to improve visualization for pipeline.
I want skip stage and mark skip stage as skip.
But using Skripted Pipeline i must approve signature.
staticMethod org.jenkinsci.plugins.pipeline.modeldefinition.Utils markStageSkippedForConditional java.lang.String
Using it:
import org.jenkinsci.plugins.pipeline.modeldefinition.Utils map_dev = ["dev", "qa", "stage" ,"perf"] prodPromoter = null map_dev.each { stage("${it}") { try{ prodPromoter = input(message: "Deploy ${it}") } catch(e){ Utils.markStageSkippedForConditional("${it}") } } }
I now that i can using Declarative Pipeline like this:
when {
expression {
try {
devPromoter = input(message: "Deploy")
} catch(e) {
return false
}
}
}
steps { }
BUT, Could you please just add Utils.markStageSkippedForConditional to @whitelist ?
Because Scripted pipleine more readable and flexible for me...
Thank you for advance!
Attachments
Issue Links
- relates to
-
-
- Closed
-
- links to
Activity
It would be great to have this feature, or at least whitelist markStageSkippedForConditional so that the method is allowed in groovy sandbox. I am trying to bring my codebase into compliance with groovy script security, but I am finding it incredibly difficult as there are features that I need to support in scripted pipeline that are only supported securely in declarative pipelines, such as markStageSkippedForConditional.
I do agree with this proposal. In addition to, there is another reason. This should prevent against the error:
"Scripts not permitted to use staticMethod org.jenkinsci.plugins.pipeline.modeldefinition.Utils markStageSkippedForConditional java.lang.String. Administrators can decide whether to approve or reject this signature.
For another, this may duplicate JENKINS-37781
PR: https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/346