Aborting a build can result in an UNKNOWN stage state

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      This is not easy to reproduce (usually if you have a long running archive you can see it sometimes).

      Using the script below may help.
      To reproduce:

      • run pipeline
      • Notice it sites in the build stage for a while
      • Press stop button when in this state
      • Note that the build stage goes purple vomit colour

      Expected behavior:

      • Should just go red, not purple vomit.

      Pipeline:

      
      node {
          stage('Checkout') {
              sh "echo 42"        
              
      
          }
      
          
          stage('Generate Plugin Data') {
              docker.image('cloudbees/java-build-tools').inside {
                  sh 'echo 42'
              }
          }
          
                  stage('Build') {
                      docker.image('cloudbees/java-build-tools').inside {
                          withEnv([
                              'DATA_FILE_URL=http://nginx/plugins.json.gzip',
                          ]) {
                              sh 'echo foo > smeg.txt'
                          }
                      }
      
                      /** archive all our artifacts for reporting later */
                      archiveArtifacts archives: '*.txt', fingerprint: true
                  }
          
      
      }
      

            Assignee:
            Vivek Pandey
            Reporter:
            Michael Neale
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: