The concepts of `node`, `stage` and `step` are different:

 - `node` specifies *where* something shall happen. You give a name or a label, and Jenkins runs the block there.

 - `stage` structures your script into a high-level sequence. Stages show up as columns in the Pipeline Stage view with average stage times and colours for the stage result.

 - `step` is one way to specify *what* shall happen. `sh` is of a similar quality, it is a different kind of action. (You can also use `build` for things that are already specified as projects.)

So `step`s can reside within `node`s, (if they don&#39;t, they are executed on the master), and `node`s and `step`s can be structured into an overall sequence with `stage`s.




It depends. Any `node` declaration allocates an executor (on Jenkins master or slave). This requires that you [`stash`](https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#code-stash-code-stash-some-files-to-be-used-later-in-the-build) and `unstash` the workspace, as another executor does not have the checked out sources available.

Several steps of the Pipeline DSL run in a flyweight executor and thus do not require to be inside a `node` block.
This might be helpful for an example such as the following, where you need to allocate multiple nodes anyway:

&lt;!-- language: java --&gt;

    stage(&quot;Checkout&quot;) {
      checkout scm
    }

    stage(&quot;Build&quot;) {
      node(&#39;linux&#39;) {
        sh &quot;make&quot;
      }
      node(&#39;windows&#39;) {
        bat &quot;whatever&quot;
      }
    }

    stage(&quot;Upload&quot;) {
      ...

Another (maybe more realistic example) would be to allocate multiple nodes in `parallel`. Then there&#39;s no need to let the `stage` call be executed in another allocated executor (aka within `node`).

Your example looks good to me. There&#39;s no need to allocate multiple `node`s within the single `stage`s, as this would be only additional overhead.

I am trying to run Nginx, but I am getting the error below:

&gt; bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a
&gt; socket in a way forbidden by its access permissions)

Please provide some help on what changes I need to do to make it working?

I have tried running on ports other than 80 and it works. but I need it to be running on 80.

Note: I am running on Windows 7 with command prompt running as Administrator.


Nginx- error: bind() to 0.0.0.0:80 failed. permission denied

In C# 6.0 the &quot;when&quot; keyword was introduced, now you&#39;re able to filter an exception in a catch block. But isn&#39;t this the same as a if statement inside a catch block? if so, isn&#39;t it just syntactic sugar or i&#39;m missing something?

For example a try catch block with the &quot;when&quot; keyword:

    try { … } 
    catch (WebException ex) when ex.Status == WebExceptionStatus.Timeout {
       //do something
    }
    catch (WebException ex) when ex.Status== WebExceptionStatus.SendFailure {
       //do something
    }
    catch (Exception caught) {…}

Or

    try { … } 
    catch (WebException ex) {
       if(ex.Status == WebExceptionStatus.Timeout) {
          //do something
       }
    }
    catch (WebException ex) {
       if(ex.Status == WebExceptionStatus.SendFailure) {
          //do something
       }
    }
    catch (Exception caught) {…}

Is the &quot;when&quot; keyword in a try catch block the same as an if statement?

I&#39;m trying to understand how to structure my Jenkins 2.7 pipeline groovy script.  I&#39;ve read through the [pipeline tutorial](https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md), but feel that it could expand more on these topics.

I can understand that a pipeline can have many `stage`s and each `stage` can have many `step`s.  But what is the difference between a `step();` and a method call inside a `stage`, say `sh([script: &quot;echo hello&quot;]);`.  Should `node`s be inside or outside of `stage`s?  Should the overall properties of a job be inside or outside a `node`?

Here is my current structure on an ubuntu master node:


    #!/usr/bin/env groovy

    node(&#39;master&#39;) {
        properties([
            [$class: &#39;BuildDiscarderProperty&#39;, strategy: [$class: &#39;LogRotator&#39;, numToKeepStr: &#39;10&#39;]]
        ]);
    
        stage &#39;Checkout&#39;
            checkout scm
    
        stage &#39;Build&#39;
            sh([script: &quot;make build&quot;]);
        
        archive(&quot;bin/*&quot;);
    }

What is the difference between a node, stage, and step in Jenkins pipelines?

I'm trying to understand how to structure my Jenkins 2.7 pipeline groovy script. I've read through the <a href="https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md" target="_blank" rel="noopener noreferrer">pipeline tutorial</a>, but feel that it could expand more on these topics.
I can understand that a pipeline can have many <code>stage</code>s and each <code>stage</code> can have many <code>step</code>s. But what is the difference between a <code>step();</code> and a method call inside a <code>stage</code>, say <code>sh([script: "echo hello"]);</code>. Should <code>node</code>s be inside or outside of <code>stage</code>s? Should the overall properties of a job be inside or outside a <code>node</code>?
Here is my current structure on an ubuntu master node:
<pre><code class="hljs language-php">#!/usr/bin/env groovy

node('master') {
 properties([
 [$class: 'BuildDiscarderProperty', strategy: [$class: 'LogRotator', numToKeepStr: '10']]
 ]);

 stage 'Checkout'
 checkout scm

 stage 'Build'
 sh([script: "make build"]);
 
 archive("bin/*");
}
</code></pre>

I&#39;m trying to create a declarative Jenkins pipeline script but having issues with simple variable declaration.

Here is my script:

    pipeline {
       agent none
       stages {
           stage(&quot;first&quot;) {
               def foo = &quot;foo&quot; // fails with &quot;WorkflowScript: 5: Expected a step @ line 5, column 13.&quot;
               sh &quot;echo ${foo}&quot;
           }
       }
    }

However, I get this error:

    org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
    WorkflowScript: 5: Expected a step @ line 5, column 13.
               def foo = &quot;foo&quot;
               ^

I&#39;m on Jenkins 2.7.4 and Pipeline 2.4.

Jenkins: Cannot define variable in pipeline stage

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

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

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

Content Type	Original Author	Original Content on Stackoverflow
Question	tarabyte	View Question on Stackoverflow
Solution 1 - Jenkins	chris_f	View Answer on Stackoverflow
Solution 2 - Jenkins	StephenKing	View Answer on Stackoverflow

What is the difference between a node, stage, and step in Jenkins pipelines?

Jenkins Problem Overview

Jenkins Solutions

Solution 1 - Jenkins

Solution 2 - Jenkins

Is the "when" keyword in a try catch block the same as an if statement?

Nginx- error: bind() to 0.0.0.0:80 failed. permission denied

Attributions