This is a huge gap in the Jenkins Pipeline capabilities IMO. Definitely hard to provide due to the fact that a pipeline is a single job. One solution might be to &quot;archive&quot; the workspace as an &quot;artifact&quot; (tar and archive **/* as &#39;workspace.tar.gz&#39;), and then have another pipeline copy the artifact and and untar it into the new workspace. This allows the second pipeline to pickup where the previous one left off. Of course there is no way to gauentee that the second pipeline cannot be executed out of turn or more than once. Which is too bad. The Delivery Pipeline Plugin really shines here. You execute a new pipeline right from the view - instead of the first job. Anyway - not much of an answer - but its the path I&#39;m going to try.

EDIT: This plugin looks promising:

https://github.com/jenkinsci/external-workspace-manager-plugin/blob/master/doc/PIPELINE_EXAMPLES.md

My class has an explicit conversion to bool:

    struct T {
        explicit operator bool() const { return true; }
    };

and I have an instance of it:

    T t;

To assign it to a variable of type `bool`, I need to write a cast:

    bool b = static_cast&lt;bool&gt;(t);
    bool b = bool(t);
    bool b(t);  // converting initialiser
    bool b{static_cast&lt;bool&gt;(t)};

I know that I can use my type directly in a conditional without a cast, despite the `explicit` qualifier:

    if (t)
        /* statement */;

Where else can I use `t` as a `bool` without a cast?

When can I use explicit operator bool without a cast?

I want to use Local or session storage to save authentication token in **`angular 2.0.0.`** I  use **`angular2-localstorage`** but it works only **angular 2.0.0-rc.5** and when I used it in 2.0.0 it through me **Type** error. I want to use default local storage of Angular 2.0.0.


How to store token in Local or Session Storage in Angular 2?

Prior Jenkins2 I was using [Build Pipeline Plugin][1] to build and manually deploy application to server. 
Old configuration:
[![jenkins-pipeline-plugin][2]][2]

That works great, but I want to use new Jenkins pipeline, generated from groovy script (Jenkinsfile), to create manual step.

So far I came up with `input` jenkins step.

Used jenkinsfile script:

    node {
       stage &#39;Checkout&#39;
       // Get some code from repository
    
       stage &#39;Build&#39;
       // Run the build
    }
    
    stage &#39;deployment&#39;
    input &#39;Do you approve deployment?&#39;
    node {
        //deploy things
    }

But this waits for user input, noting that build is not completed. I could add timeout to `input`, but this won&#39;t allow me to pick/trigger a build and deploy it later on:


[![jenkins-pipeline][3]][3]

How can I achive same/similiar result for manual step/trigger with new jenkins-pipeline as prior with Build Pipeline Plugin?


  [1]: https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin
  [2]: http://i.stack.imgur.com/ruBF8.png
  [3]: http://i.stack.imgur.com/Xkgjo.png

Jenkins how to create pipeline manual step

Prior Jenkins2 I was using <a href="https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin" target="_blank" rel="noopener noreferrer">Build Pipeline Plugin</a> to build and manually deploy application to server.
Old configuration:
<a href="http://i.stack.imgur.com/ruBF8.png" target="_blank" rel="noopener noreferrer"><img src="http://i.stack.imgur.com/ruBF8.png" alt="jenkins-pipeline-plugin"></a>
That works great, but I want to use new Jenkins pipeline, generated from groovy script (Jenkinsfile), to create manual step.
So far I came up with <code>input</code> jenkins step.
Used jenkinsfile script:
<pre><code class="hljs language-arduino">node {
 stage 'Checkout'
 // Get some code from repository

 stage 'Build'
 // Run the build
}

stage 'deployment'
input 'Do you approve deployment?'
node {
 //deploy things
}
</code></pre>
But this waits for user input, noting that build is not completed. I could add timeout to <code>input</code>, but this won't allow me to pick/trigger a build and deploy it later on:
<a href="http://i.stack.imgur.com/Xkgjo.png" target="_blank" rel="noopener noreferrer"><img src="http://i.stack.imgur.com/Xkgjo.png" alt="jenkins-pipeline"></a>
How can I achive same/similiar result for manual step/trigger with new jenkins-pipeline as prior with Build Pipeline Plugin?

I&#39;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&#39;t figure out how to make it work.

Here is the directory structure I&#39;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 repo checked out. With the Multiple SCM, I used git, and then added the &quot;checkout to a subdirectory&quot; behavior. Here was my attempt with a pipeline script:

    node(&#39;ATLAS &amp;&amp; Linux&#39;) {
        sh(&#39;[ -e CalibrationResults ] || mkdir CalibrationResults&#39;)
        sh(&#39;cd CalibrationResults&#39;)
        git url: &#39;https://github.com/AtlasBID/CalibrationResults.git&#39;
        sh(&#39;cd ..&#39;)
        sh(&#39;[ -e Combination ] || mkdir Combination&#39;)
        sh(&#39;cd Combination&#39;)
        git url: &#39;https://github.com/AtlasBID/Combination.git&#39;
        sh(&#39;cd ..&#39;)
        sh(&#39;[ -e CombinationBuilder ] || mkdir CombinationBuilder&#39;)
        sh(&#39;cd CombinationBuilder&#39;)
        git url: &#39;https://github.com/AtlasBID/CombinationBuilder.git&#39;
        sh &#39;cd ..&#39;
    
        sh(&#39;ls&#39;)
        sh(&#39;. CombinationBuilder/build.sh&#39;)
    }

However, the git command seems to execute at the top level directory of the workspace (which makes some sense), and according to the syntax too, there doesn&#39;t seem to be the checkout-to-sub-directory behavior.

Using a Jenkins pipeline to checkout multiple git repos into same job

I have a series of stages that perform quick checks.  I want to perform them all, even if there are failures.  For example:

    stage(&#39;one&#39;) {
        node {
            sh &#39;exit 0&#39;
        }
    }
    stage(&#39;two&#39;) {
        node {
            sh &#39;exit 1&#39;   // failure
        }
    }
    stage(&#39;three&#39;) {
        node {
            sh &#39;exit 0&#39;
        }
    }

Stage `two` fails, so by default stage `three` is not executed.

Ordinarily this would be a job for `parallel`, but I want to display them in the stage view.  In the mock up below:

- Build #4 shows what normally happens.  Job `two` fails so `three` does not run.
- I Photoshopped Build #6 to show what I would like to see.  Job `two` fails and is displayed as such, but `three` still runs.  The real Jenkins would probably display the entire Build #6 tinged slightly red, which is of course fine.


[![Mock up of desired Stage View result][1]][1]


  [1]: https://i.stack.imgur.com/JULvA.png

Continue Jenkins pipeline past failed stage

I use Jenkins and Multibranch Pipeline. I have a job for each active git branch.
New build is triggered by push in git repository. What I want is to abort running builds in current branch if new one appears in same branch. 

For example: I commit and push to branch `feature1`. Then `BUILD_1` started in Jenkins. I make another commit and push to branch `feature1` while `BUILD_1` is still running. I want `BUILD_1` to be aborted and to start `BUILD_2`. 

I tried to use `stage concurrency=x` option, and [stage-lock-milestone](https://jenkins.io/blog/2016/10/16/stage-lock-milestone/) feature, but didn&#39;t manage to solve my problem.

Also I&#39;ve read this thread https://stackoverflow.com/questions/10280846/stopping-jenkins-job-in-case-newer-one-is-started, but there is no solution for my problem.

Do you know any solution to this?


Jenkins - abort running build if new one is started

For running an ASP.NET Core application, I generated a dockerfile which build the application and copys the source code in the container, which is fetched by Git using Jenkins. So in my workspace, I do the following in the dockerfile: 

    WORKDIR /app
    COPY src src

While Jenkins updates the files on my host correctly with Git, Docker doesn&#39;t apply this to my image. 

My basic script for building:

    #!/bin/bash
    imageName=xx:my-image
    containerName=my-container
    
    docker build -t $imageName -f Dockerfile  .
    
    containerRunning=$(docker inspect --format=&quot;{{ .State.Running }}&quot; $containerName 2&gt; /dev/null)
    
    if [ &quot;$containerRunning&quot; == &quot;true&quot; ]; then
            docker stop $containerName
            docker start $containerName
    else
            docker run -d -p 5000:5000 --name $containerName $imageName
    fi

I tried different things like `--rm` and `--no-cache` parameter for `docker run` and also stopping/removing the container *before* the new one is build. I&#39;m not sure what I&#39;m doing wrong here. It seems that docker is updating the image correctly, as the call of `COPY src src` would result in a layer id and no cache call: 

    Step 6 : COPY src src
     ---&gt; 382ef210d8fd

What is the recommended way to update a container? 

My typical scenario would be: The application is running on the server in a Docker container. Now parts of the app are updated, e.g. by modifying a file. Now the container should run the new version. Docker seems to recommend building a new image instead of modifying a existing container, so I think the general way of rebuilding like I do is right, but some detail in the implementation has to be improved. 

Rebuild Docker container on file changes

I am looking at limiting the number of concurrent builds to a specific number in Jenkins, leveraging the multibranch pipeline workflow but haven&#39;t found any good way to do this in the docs or google.

Some docs say this can be accomplished using concurrency in the `stage` step of a Jenkinsfile but I&#39;ve also [read elsewhere][1] that that is a deprecated way of doing it.

It looks like there was [something released][2] fairly recently for limiting concurrency via `Job Properties` but I couldn&#39;t find documentation for it and I&#39;m having trouble following the code.  The only thing I found a [PR][3] that shows the following:

`properties([concurrentBuilds(false)])`

But I am having trouble getting it working.

Does anybody know or have a good example of how to limit the number of concurrent builds for a given, multibranch project?  Maybe a Jenkinsfile snippet that shows how to limit or cap the number of multibranch concurrent builds?


  [1]: https://jenkins.io/blog/2016/10/16/stage-lock-milestone/
  [2]: https://issues.jenkins-ci.org/browse/JENKINS-34547
  [3]: https://github.com/jenkinsci/workflow-job-plugin/pull/8

How to limit Jenkins concurrent multibranch pipeline builds?

I&#39;m running: 

 - IntelliJ Ultimate 2016.3
 - Homebrew 1.1.2
 - OS X 10.11.5 El Capitan 

I ran `brew install groovy` which resulted in groovy being installed in `/usr/local/Cellar/groovy/2.4.7/`. Brew also added a symlink: `/usr/local/bin/groovy -&gt; ../Cellar/groovy/2.4.7/bin/groovy`


When I open the groovy project in IntelliJ, it gives me an option to Configure a Groovy SDK. I haven&#39;t set this up yet, so I get a &quot;Create&quot; button, which launches finder. From what I can tell there&#39;s nothing that I can select to make IntelliJ happy. I&#39;ve tried `/user/local/bin/groovy`, `/user/local/Cellar/groovy`, `/user/local/Cellar/groovy/2.4.7`, `/user/local/Cellar/groovy/2.4.7/bin` etc. No mater which I choose, IntelliJ doesn&#39;t accept the library and continues to tell me &quot;Error: library is not specified&quot;. 

Does anyone know how I&#39;m supposed to go about telling IntelliJ where groovy is? 

How do I tell IntelliJ about groovy installed with brew on OSX

The structure of my Gradle project is the following:

    Project
    ├── app
         └── build.gradle
    ├── foo
         └── bar.txt
    &#183;
    &#183;
    &#183;
    └── build.gradle

Normally to get the absolute path of the `foo` folder I can just simply do `new File(&#39;foo&#39;).getAbsolutePath()` in the root `build.gradle` file.

But this unfortunately doesn&#39;t work if you run the gradle script from outside the project directory, for example doing something like this:

    $ trunk/gradlew -b trunk/build.gradle tasks

With the previous command gradle is looking for the `foo` directory in the parent of the Project, because I started the script from there.

Is there a way to get the absolute path of the Project where the build.gradle is, even if you start your script from another directory? Or is there any other way to get a reference of a directory in the same folder where the script is?

I&#39;ve tried also with `getClass().protectionDomain.codeSource.location.path` but it is returning the path to the gradle cache directory.

Gradle: getting the root project directory path when starting with a custom build file

I&#39;m trying to create a task with a function inside:

    def doCopyMibArtefactsHere(projectName) {
        step ([
            $class: &#39;CopyArtifact&#39;,
            projectName: $projectName,
            filter: &#39;**/**.mib&#39;,
            fingerprintArtifacts: true, 
            flatten: true
        ]);
    }
    
    def BuildAndCopyMibsHere(projectName, params) {
        build job: $project, parameters: $params
        doCopyMibArtefactsHere($projectName)
    }
    
    
    node { 
        stage(&#39;Prepare Mib&#39;){
            BuildAndCopyMibsHere(&#39;project1&#39;)
        }
    }

But this gives me an exception:

&gt; java.lang.NoSuchMethodError: No such DSL method &#39;BuildAndCopyMibsHere&#39; found among steps*

**Is there any way to use embedded functions within a Pipeline script?**

How to define and use function inside Jenkins Pipeline config?

What is the difference between an **agent** and a **node** in a jenkins pipeline?

I&#39;ve found those definitions:

 - [Node][1]: A Pipeline performs most of the work in the context of one or more declared node steps.
 - [Agent][2]: The agent directive specifies where the entire Pipeline, or a specific stage, will execute in the Jenkins environment depending on where the agent directive is placed.

So both are used for executing pipeline steps. But when to use which one?

  [1]: https://jenkins.io/doc/book/pipeline/
  [2]: https://jenkins.io/doc/book/pipeline/syntax/#agent

Content Type	Original Author	Original Content on Stackoverflow
Question	Zigac	View Question on Stackoverflow
Solution 1 - Jenkins	Michael Andrews	View Answer on Stackoverflow

Jenkins how to create pipeline manual step

Jenkins Problem Overview

Jenkins Solutions

Solution 1 - Jenkins

How to store token in Local or Session Storage in Angular 2?

When can I use explicit operator bool without a cast?

Attributions