TL;DR variables defined with def in the main script body cannot be accessed from other methods. variables defined without def can be accessed directly by any method even from different scripts. It’s a bad practice. variables defined with def and @Field annotation can be accessed directly from methods defined in the same script. Explanation When … Read more
Now, the sh step supports returning stdout by supplying the parameter returnStdout. // These should all be performed at the point where you’ve // checked out your sources on the slave. A ‘git’ executable // must be available. // Most typical, if you’re not cloning into a sub directory gitCommit = sh(returnStdout: true, script: ‘git … Read more
Pipeline plugin You can use the Pipeline Plugin (formerly workflow-plugin). It comes with many examples, and you can follow this tutorial. e.g. // build stage ‘build’ … // deploy stage ‘deploy’ … // run tests in parallel stage ‘test’ parallel ‘functional’: { … }, ‘performance’: { … } // promote artifacts stage ‘promote’ … Build … Read more
The issue you’re seeing is likely related to recent security fixes. See the Configuring Content Security Policy wiki page for details on how to relax the Jenkins configuration. The CSP header sent by Jenkins can be modified by setting the system property hudson.model.DirectoryBrowserSupport.CSP: If its value is the empty string, e.g. java -Dhudson.model.DirectoryBrowserSupport.CSP= -jar jenkins.war … Read more
I guess this is by design, “result can only get worse” in setResult(): // result can only get worse if (result==null || r.isWorseThan(result)) { result = r; LOGGER.log(FINE, this + ” in ” + getRootDir() + “: result is set to ” + r, LOGGER.isLoggable(Level.FINER) ? new Exception() : null); } That’s a bummer
I think the variable is available directly, rather than through env, when using Workflow plugin. Try: node() { print “DEBUG: parameter foo = ${foo}” }
I was trying to reduce duplicated code in my existing Jenkinsfile using declarative pipeline syntax. Finally I was able to wrap my head around the difference between scripted and declarative syntax. It is possible to use scripted pipeline syntax in a declarative pipeline by wrapping it with a script {} block. Check out my example … Read more
Jenkins by default has CSRF Protection enabled which prevents one-click attacks. To invoke the request, you need to obtain the crumb from /crumbIssuer/api/xml using your credentials and include it into your request. For example: CRUMB=$(curl -s ‘http://USER:TOKEN@localhost:8080/crumbIssuer/api/xml?xpath=concat(//crumbRequestField,”:”,//crumb)’) Then you can create a job (by including the crumb into your header): curl -X POST -H “$CRUMB” … Read more
This is now possible, even with declarative pipelines: pipeline { agent any stages { stage(‘1’) { steps { sh ‘exit 0’ } } stage(‘2’) { steps { catchError(buildResult: ‘SUCCESS’, stageResult: ‘FAILURE’) { sh “exit 1” } } } stage(‘3’) { steps { sh ‘exit 0’ } } } } In the example above, all stages … Read more
In addition to the above mentioned answers: I wanted to start a job with a simple parameter passed to a second pipeline and found the answer on http://web.archive.org/web/20160209062101/https://dzone.com/refcardz/continuous-delivery-with-jenkins-workflow So i used: stage (‘Starting ART job’) { build job: ‘RunArtInTest’, parameters: [[$class: ‘StringParameterValue’, name: ‘systemname’, value: systemname]] }