jenkins-pipeline

Here's the code I'm playing with node { stage 'build' echo 'build' stage 'tests' echo 'tests' stage 'end-to-end-tests' def e2e = build job:'end-to-end-tests', propagate: false result = e2e.result if (result.equals("SUCCESS")) { stage 'deploy' build 'deploy' } else { ?????? I want to just fail this stage } } Is there any way for me to mark the 'end-to-end-tests' stage as failed without failing the whole job? Propagate false just always marks the stage as true, which is not what I want, but Propagate true marks the job as failed which I also don't want. Stage takes a block now, so wrap the stage

I have the following build pipeline set up as a job: Stage 1 - verify all dependencies exist Stage 2 - build the new jar Stage 3 - Run integration tests Stage 4 - Deploy to staging environment (manual step) Stage 5 - Deploy to production environment (manual step) I am looking for a way to start the build pipeline from a particular stage in case of a transient failure. For example, let's say there was a network issue when the user clicked to deploy to production. I don't think it makes sense to start the pipeline from stage 1... I'd like to try that step again and continue on from there in the

I'm using the Jenkins Multiple SCM plugin to check out three git repositories into three sub directories in my Jenkins job. I then execute one set of commands to build a single set of artifacts with information and code drawn from all three repositories. Multiple SCM is now depreciated, and the text recommends moving to pipelines. I tried, but I can't figure out how to make it work. Here is the directory structure I'm interested in seeing from the top level of my Jenkins job directory: $ ls Combination CombinationBuilder CombinationResults Each of those three sub-directories has a single git

How do I pass variables between stages in a declarative pipeline? In a scripted pipeline, I gather the procedure is to write to a temporary file, then read the file into a variable. How do I do this in a declarative pipeline? E.g. I want to trigger a build of a different job, based on a variable created by a shell action. stage("stage 1") { steps { sh "do_something > var.txt" // I want to get var.txt into VAR } } stage("stage 2") { steps { build job: "job2", parameters[string(name: "var", value: "${VAR})] } } If you want to use a file (since a script is the thing generating the value you need)

We have several Java projects. Each project has its own delivery pipeline. All pipelines have the following steps in common (simplified): Build project Release project Deploy to test environment Deploy to production environment The project pipelines only differ in project specific properties such as service names or the IP addresses of test and production environment. The questions are: How could we avoid the boilerplate that all projects have in common? Does Jenkins "Pipeline as code" provide something like pipeline templates? I could imagine that a template would save a lot of redundant code

Solved : Thanks to below answer from S.Richmond. I needed to unset all stored maps of the groovy.json.internal.LazyMap type which meant nullifying the variables envServers and object after use. Additional : People searching for this error might be interested to use the Jenkins pipeline step readJSON instead - find more info here . I am trying to use Jenkins Pipeline to take input from the user which is passed to the job as json string. Pipeline then parses this using the slurper and I pick out the important information. It will then use that information to run 1 job multiple times in parallel