Code changed in jenkins
User: Andrew Bayer
Path:
pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/steps/ValidateDeclarativePipelineStep.java
pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java
pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/steps/ValidateDeclarativePipelineStepTest.java
pipeline-model-definition/src/test/resources/validateDeclarativePipelineStep.groovy
http://jenkins-ci.org/commit/pipeline-model-definition-plugin/bc6c17770181604fc648d775c6adb2162c9a4e2f
Log:
[FIXED JENKINS-42168] Add validateDeclarativePipeline(path) step
Given a path to a file containing a Declarative Pipeline to validate,
this will read that file from the workspace, validate its contents,
echo out relevant errors to the build log, and return true if the
contents validated, or false other wise.
+1, I think the use case for CLI is still valid to be able to validate your work on your dev box progressively/before pushing. But would make life easier to have a pipeline step: we would then have more easily a PR build for modifications against Jenkinsfile itself.
Thanks!