Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43578

Declarative pipeline: post section doesn't play nice with agent none

XMLWordPrintable

      Hi, so using the declarative pipeline it appears if you have agent none set at the top of the pipeline and agents defined per stage, you are unable to have a post section that executes certain steps (that require a node context). The following will result in an error::

      pipeline {
    agent none
    stages {
        stage('Example') {
            steps {
                echo 'Hello World'
            }
        }
    }
    post { 
        always { 
            deleteDir()
        }
    }
}

      Required context class hudson.FilePath is missing
Perhaps you forgot to surround the code with a step that provides this, such as: node

ERROR: Attempted to execute a step that requires a node context while agent none was specified. Be sure to specify your own node { ... } blocks when using agent none.

      I'm guessing its expected behavior but would it be possible to associate an agent with the post section as we do with stages?

      Thanks, David

       

          [JENKINS-43578] Declarative pipeline: post section doesn't play nice with agent none

          david shepard created issue -
          david shepard made changes -
          Description Original: Hi, so using the declarative pipeline it appears if you have *agent none* set at the top of the pipeline and agents defined per stage, you are unable to have a *post* section that executes certain steps (that require a node context). For example:
          {code:java}
          pipeline {
              agent none
              stages {
                  stage('Example') {
                      steps {
                          echo 'Hello World'
                      }
                  }
              }
              post {
                  always {
                      deleteDir()
                  }
              }
          }
          {code}
          I'm guessing its expected behavior but would it be possible to associate an agent with the *post* section as we do with stages?

          Thanks, David

                      		New: Hi, so using the declarative pipeline it appears if you have *agent none* set at the top of the pipeline and agents defined per stage, you are unable to have a *post* section that executes certain steps (that require a node context). The following will result in an error::
          {code:java}
          pipeline {
              agent none
              stages {
                  stage('Example') {
                      steps {
                          echo 'Hello World'
                      }
                  }
              }
              post {
                  always {
                      deleteDir()
                  }
              }
          }
          {code}
          {code:java}
          Required context class hudson.FilePath is missing
          Perhaps you forgot to surround the code with a step that provides this, such as: node

          ERROR: Attempted to execute a step that requires a node context while agent none was specified. Be sure to specify your own node { ... } blocks when using agent none.{code}
          I'm guessing its expected behavior but would it be possible to associate an agent with the *post* section as we do with stages?

          Thanks, David

           
          david shepard made changes -
          Rank New: Ranked higher
          Andrew Bayer made changes -
          Component/s Original: pipeline [ 21692 ]
          Andrew Bayer made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Liam Newman made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          Nicholas Brown made changes -
          Link New: This issue relates to JENKINS-64874 [ JENKINS-64874 ]

            abayer Andrew Bayer
            davidshepard77 david shepard
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: