jenkins-pipeline

We are now experimenting with multi-branch Pipeline builds. The main advantage of the feature is that it allows us to automatically create new Jenkins jobs whenever a new branch is created. However, it also is a bit more difficult to implement than the old way of selecting how to do the build using the UI. Plus, certain features seem to be missing. For example, in Jenkins Freestyle jobs, we are able to use the Jenkins UI to browse through the workspace, download individual files, and even wipe out the workspace. We found this helpful when builds went awry or if the developer needed a

I've a group of multibranch pipeline jobs generated with the following piece groovy script: [ 'repo1', 'repo2', ].each { service -> multibranchPipelineJob(service) { displayName(service) branchSources { git { remote("git@gitlab.com:whatever/${service}.git") credentialsId('gitlab-ssh-key') } } orphanedItemStrategy { discardOldItems { daysToKeep(0) numToKeep(30) } } triggers { periodic(5) } } } and in each repo a Jenkinsfile that looks as follows: #!/usr/bin/env groovy properties([ gitLabConnection('ci@gitlab.com'), pipelineTriggers([ [ $class : 'GitLabPushTrigger', triggerOnPush : true,

I'm rebuilding an existing build pipeline as a jenkins declarative pipeline (multi-branch-pipeline) and have a problem handling build propagation. After packaging and stashing all relevant files the pipeline is supposed to wait for user input to trigger deployment. If i just add an input step the current build-node is blocked. As this executor is pretty heavy i would like to move this step to a more lightweight machine. Initially i did the job as a scripted pipeline and just created two different node('label') blocks. is there a way for me to do something similar with the declarative syntax?

I have a Jenkinsfile or a Jenkins pipeline which creates a new image and starts a container out of that image. It works well for the first time. But on subsequent runs, I want the previous container to be stopped and removed. My Jenkinsfile is as follows: node { def commit_id stage('Preparation') { checkout scm sh "git rev-parse --short HEAD > .git/commit-id" commit_id = readFile('.git/commit-id').trim() } stage('docker build/push') { docker.withRegistry('https://index.docker.io/v1/', 'dockerhub') { def app = docker.build("my-docker-id/my-api:${commit_id}", '.').push() } } stage('docker stop

I am using Jenkinsfile for scripting of a pipeline. Is there any way to disable printing of executed shell commands in build logs? Here is just a simple example of a jenkins pipeline: node{ stage ("Example") { sh('echo shellscript.sh arg1 arg2') sh('echo shellscript.sh arg3 arg4') } } which produces the following output in console log: [Pipeline] node Running on master in /var/lib/jenkins/workspace/testpipeline [Pipeline] { [Pipeline] stage [Pipeline] { (Test) [Pipeline] sh [testpipeline] Running shell script + echo shellscript.sh arg1 arg2 shellscript.sh arg1 arg2 [Pipeline] sh [testpipeline]

I have a declarative pipeline script for my multibranch project in which I would like to read a text file and store the result as a string variable to be accessed by a later step in the pipeline. Using the snippet generator I tried to do something like this: filename = readFile 'output.txt' For which filename would be my string. I get an error in the Jenkins console output: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 30: Expected a step @ line 30, column 5. filename = readFile 'output.txt' Do I need to use a withEnv step to set the output of

I have a Jenkins pipeline job that archives an Artifact in its first phase, I then need to copy that Artifact in another stage of the pipeline build node { stage 'Stage 1 of build' // Run tests, if successful archive the artifact archiveArtifacts artifacts: 'build/test.js', excludes: null stage 'Stage 2 of build' // want to copy artifact from stage 1 of the build step([$class: 'CopyArtifact', filter: 'build/test.js', fingerprintArtifacts: true, flatten: true, projectName: 'echo-develop-js-pipeline', selector: [$class: 'WorkspaceSelector'], target: './client/public/vendor/echo/']) } With this I