If your Jenkinsfile and groovy file in one repository and Jenkinsfile is loaded from SCM you have to do: Example.Groovy def exampleMethod() { //do something } def otherExampleMethod() { //do something else } return this JenkinsFile node { def rootDir = pwd() def exampleModule = load “${rootDir}@script/Example.Groovy ” exampleModule.exampleMethod() exampleModule.otherExampleMethod() }
Use multibranch pipeline job type, not the plain pipeline job type. The multibranch pipeline jobs do posess the environment variable env.BRANCH_NAME which describes the branch. In my script.. stage(‘Build’) { node { echo ‘Pulling…’ + env.BRANCH_NAME checkout scm } } Yields… Pulling…master
The env.BRANCH_NAME variable contains the branch name. As of Pipeline Groovy Plugin 2.18, you can also just use BRANCH_NAME (env isn’t required but still accepted.)
Newer versions of the declarative pipelines support this, while this was not possible before (~mid 2017). You can just declare functions as you’d expect it from a groovy script: pipeline { agent any stages { stage(‘Test’) { steps { whateverFunction() } } } } void whateverFunction() { sh ‘ls /’ }
Since version 2.5 of the Pipeline Nodes and Processes Plugin (a component of the Pipeline plugin, installed by default), the WORKSPACE environment variable is available again. This version was released on 2016-09-23, so it should be available on all up-to-date Jenkins instances. Example node(‘label’){ // now you are on slave labeled with ‘label’ def workspace … Read more
The answer provided in https://stackoverflow.com/a/43963315/6839445 is deprecated. The current method to disable concurrent builds is to set options: options { disableConcurrentBuilds() } Detailed description is available here: https://jenkins.io/doc/book/pipeline/syntax/#options
You can use the dir command to execute a pipeline step in a subdirectory: node(‘ATLAS && Linux’) { dir(‘CalibrationResults’) { git url: ‘https://github.com/AtlasBID/CalibrationResults.git’ } dir(‘Combination’) { git url: ‘https://github.com/AtlasBID/Combination.git’ } dir(‘CombinationBuilder’) { git url: ‘https://github.com/AtlasBID/CombinationBuilder.git’ } sh(‘ls’) sh(‘. CombinationBuilder/build.sh’) }
I think the variable is available directly, rather than through env, when using Workflow plugin. Try: node() { print “DEBUG: parameter foo = ${foo}” }
This is now possible. Below is an example of a declarative pipeline, but catchError works for scripted pipelines as well. 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 … Read more
As for declarative syntax, you can use the options block: pipeline { options { buildDiscarder(logRotator(numToKeepStr: ’30’, artifactNumToKeepStr: ’30’)) } … } Parameters for logRotator (from the source code): daysToKeepStr: history is only kept up to this days. numToKeepStr: only this number of build logs are kept. artifactDaysToKeepStr: artifacts are only kept up to this days. … Read more