jenkins-pipeline

We utilize the pipeline and after the build completes successfully we are running the following: bat "mvn sonar:sonar -B -s ${buildSettings} -Dsonar.analysis.mode=preview -Dsonar.skipDesign=true -Dsonar.report.export.path=sonar-report.json" sonarToGerrit(severity: 'Major', postScore: true, category: 'Code-Review', newIssuesOnly: true, issuesScore: '0', noIssuesScore: '0', changedLinesOnly: true) The below build log shows that it found a good number of issues but yet the issues to be commented is 0. Build log Other posts suggest that it may not be finding the report but I don't believe it's the

I'm looking for a way to run Jenkins jobs/build inside Jenkins slaves, dynamically (on-demand) started docker. Attaching schema for visual understanding. What I'm actually looking for and my flow looks like: 1) Triggering Jenkins job (manually/git/gerrit) 2) Jenkins master (running in docker) starts slave machine docker (and pass script/instructions of the build) 3) Build is running on Jenkins slave (or slaves if parallel/pipeline) 4) Result returned to Jenkins master 5) Jenkins slave docker stops Is it possible to do it this way? Docker slave image creation steps like installing openssh, user

I have a list in groovy, defined as env.list = ["abc","def"] If I try using this in a for loop for (letters in env.list) { print("Letter is $letters") } It will iterate over each letter and print the following - Letter is [ Letter is " Letter is a ..... If I define the list as follows - list = ["abc","def"] It will treat this as a list. The for loop will print the following. Letter is abc Letter is def Was using groovy to run my Jenkins pipeline. Why is there a difference based on the name? How can we define a list using a variable name with a dot (.)? in jenkins pipeline the env - is a

I have Jenkins 2.19.4 with Pipeline: Declarative Agent API 1.0.1. How does one use readProperties if you cannot define a variable to assign properties read to? For example, to capture SVN revision number, I currently capture it with following in Script style: ``` echo "SVN_REVISION=\$(svn info ${svnUrl}/projects | \ grep Revision | \ sed 's/Revision: //g')" > svnrev.txt ``` def svnProp = readProperties file: 'svnrev.txt' Then I can access using: ${svnProp['SVN_REVISION']} Since it is not legal to def svnProp in Declarative style, how is readProperties used? You can use the script step inside

We are using the Git Plugin : https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin Currently, via webhooks we start a Jenkins build whenever a change is pushed to GitHub. Now we want to trigger the same build when a new tag is added. So we have two triggering conditions : A code change is pushed to GitHub A tag is created If we try the fix mention in this thread then the builds start only for tags. jenkins trigger build if new tag is released How can we do it for both scenarios ? Question # 02 : How can we get the tag name inside a Jenkins build, is there any environment variable for it. 4

I have a jenkins server that is configured using https://github.com/shierro/jenkins-docker-examples/tree/master/05-aws-ecs I am running a blue ocean pipeline using a simple Jenkinsfile and the jenkins NodeJS plugin pipeline { agent any tools { nodejs 'node10' } stages { stage ('Checkout Code') { steps { checkout scm } } stage ('Install dependencies') { steps { sh "echo $PATH" sh "npm install" } } } } I made sure to add the node10 global tool as well w/c is used above When the pipeline gets to the script sh "npm install" i am running through this error this is the output of the command echo