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

For not existing Docker image pipeline result is Aborted instead of Failure

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • kubernetes-plugin
    • None

      For not existing Docker image pipeline shows the error:

      15:46:14 ERROR: Unable to pull Docker image "***someImage". Check if image tag name is spelled correctly.
      15:46:14 [Pipeline] // node 15:46:14 [Pipeline] } 15:46:14 [Pipeline] // podTemplate 15:46:14 [Pipeline] } 15:46:14 [Pipeline] // stage 15:46:14 [Pipeline] stage 15:46:14 [Pipeline] { (DEPLOY DEV) 15:46:14 Stage "DEPLOY DEV" skipped due to earlier failure(s)
      skipping next stages is expected behavior, but at the end  we are getting
      15:46:18 [Pipeline] End of Pipeline*15:46:18* Queue task was cancelled*15:46:19* 15:46:19 GitHub has been notified of this commit's build result*15:46:19* 15:46:19 Finished: ABORTED

       Finished: ABORTED, but Finished: FAILURE - is expected due to the error.

      Here is a merged previously PR related to the current behavior,
       
      https://github.com/jenkinsci/kubernetes-plugin/pull/497/files/2c88ebb7d79f8035fca358fb5e44be0f2bfadd56#diff-0ce113e11297cc4abbc8eabb30a712be6cd66546037dd1102d4e22380c034160

      I see the unit tests that verify the build result as Failure, but we have not that behavior.

      The plugin version: 3900.va_dce992317b_4

            Unassigned Unassigned
            ilya937 Ilya
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: