jenkins-pipeline

While using Groovy based pipelines in Jenkins you can trigger child jobs using the the build stage . Still the documentation above states nothing regarding what kind of return object you would get and what attributes it has. The only thing I found so far is that I can use build.getResult() to obtain the result of the triggered job. Still, I do want to obtain the URL of this job. From the documentation for the build step in /pipeline-syntax ( waitFormCompletion argument, the original has better formatting): You may ask that this Pipeline build wait for completion of the downstream build. In

I want to execute a "SonarQube Scanner" Step within my Jenkins 2.x Pipeline. When I try to create a sample groovy within the pipeline-syntax I only get a groovy script of the following format: step <object of type hudson.plugins.sonar.SonarRunnerBuilder> Does anyone know what is the correct Step Syntax? E.g. Publish JUnit Report looks like step([$class: 'JUnitResultArchiver', testResults: '']) I use the following Versions: Jenkins 2.11 SonarQube Scanner 2.6.1 SonarQube Plugin 2.4.1 I think I got it. First you have to retrieve your SonarQube Scanner Tool def sonarqubeScannerHome = tool name:

Anyone have a Jenkins Pipeline script that can stuff all the changes since the previous successful build in a variable? I'm using git and a multibranch pipeline job. Well I managed to cobble something together. I'm pretty sure I you can iterate the arrays better but here's what I've got for now: node('Android') { passedBuilds = [] lastSuccessfulBuild(passedBuilds, currentBuild); def changeLog = getChangeLog(passedBuilds) echo "changeLog ${changeLog}" } def lastSuccessfulBuild(passedBuilds, build) { if ((build != null) && (build.result != 'SUCCESS')) { passedBuilds.add(build)

When I run the following code on the Jenkins workflow (Jenkins 1.609.1 ,workflow 1.8) I get error of 'NotSerializableException' (also below). However, if I move the "build job" outside the "for" scope it works fine (the job is activated). Any ideas why this behavior? node('master') { ws('/opt/test) { def file = "/ot.property" def line = readFile (file) def resultList = line.tokenize() for(item in resultList ) { build job: 'testjob_1' } } } Got error: Running: End of Workflow java.io.NotSerializableException: java.util.ArrayList$Itr at org.jboss.marshalling.river.RiverMarshaller.doWriteObject

With jenkins build flow plugin this was possible: ignore(FAILURE){ build( "system-check-flow" ) } How to do this with Declarative Pipeline syntax? To ignore a failed step in declarative pipeline you basically have two options: Use script step and try-catch block (similar to previous proposition by R_K but in declarative style) stage('someStage') { steps { script { try { build job: 'system-check-flow' } catch (err) { echo err } } echo currentBuild.result } } Use catchError stage('someStage') { steps { catchError { build job: 'system-check-flow' } echo currentBuild.result } } In both cases the

I am trying to get a prebuild merge to work inside a multibranch pipeline and I would like to avoid having to hardcode the git url in my pipeline script. It seems like scm step must store the url somehow, but I cannot figure out how to access it. You are correct, the scm object does have the information you need. When using git as the source control in a Pipeline project (or Multibranch Pipeline project), the scm global variable will be an instance of GitSCM . That means that `scm.getUserRemoteConfigs()' will return a list of UserRemoteConfig instances. Those instances have the git remote's

I'm trying to replicate the equivalent of a conditional stage in Jenkins pipeline using a try / catch around a preceding stage, which then sets a success variable, which is used to trigger the conditional stage. It appears that a try catch block is the way to go, setting a success var to SUCCESS or FAILED, which is used as part of a when statement later (as part of the conditional stage). The code I am using is as follows: pipeline { agent any stages { try{ stage("Run unit tests"){ steps{ sh ''' # Run unit tests without capturing stdout or logs, generates cobetura reports cd ./python