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

Step not marked as failure when step could not be found

    • Declarative - 1.2, Declarative backlog

      This shows up primarily in Blue Ocean, it appears that whatever is happening in Declarative Pipeline when a step is resolved, it does not appear to mark the current step as failed when resolution failed.

      See the attached screenshot in case that awful description wasn't clear

      What I would expect: the last "General" build step to also be marked as a failure.

          [JENKINS-44491] Step not marked as failure when step could not be found

          R. Tyler Croy created issue -

          Andrew Bayer added a comment -

          Hrrrrm. this needs further investigation.

          Andrew Bayer added a comment - Hrrrrm. this needs further investigation.
          James Dumay made changes -
          Sprint New: Declarative - 1.2 [ 366 ]
          James Dumay made changes -
          Rank New: Ranked higher

          James Dumay added a comment -

          abayer feels related to the current batch of work you are hacking on?

          James Dumay added a comment - abayer feels related to the current batch of work you are hacking on?
          Andrew Bayer made changes -
          Sprint Original: Declarative - 1.2 [ 366 ] New: Declarative - 1.2, Declarative backlog [ 366, 621 ]
          Sakis Kechlimparis made changes -
          Rank New: Ranked higher
          Andrew Bayer made changes -
          Assignee Original: Andrew Bayer [ abayer ]

            Unassigned Unassigned
            rtyler R. Tyler Croy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: