[JENKINS-32146] Last step misleadingly marked as blue even though build status is FAILURE

[jenkins-infra-bot]

I created a small project https://github.com/ngiger/jenkins-bug which produces contains two ArtifactArchivers steps. Both have fingreprinting enabled.

I created a Multibranch Worksflow project, using the Jenkinsfile from the github project mentioned aboed.

The first step one completes successfully, as the file exist.

The second step one references a non existing file. All steps of the build have the blue icon, but inside the build.xml I see only one line
FAILURE
whereas the successful step had



README.md
3f7c3b7d5e5d582a09643416b80fafaf

---

Originally reported by ngiger, imported from: Last step misleadingly marked as blue even though build status is FAILURE

• assignee: jglick
• status: Open
• priority: Minor
• component(s): workflow-support-plugin
• resolution: Unresolved
• votes: 0
• watchers: 4
• imported: 20260601-173816

Raw content of original issue

I created a small project https://github.com/ngiger/jenkins-bug which produces contains two ArtifactArchivers steps. Both have fingreprinting enabled.

I created a Multibranch Worksflow project, using the Jenkinsfile from the github project mentioned aboed.

The first step one completes successfully, as the file exist.

The second step one references a non existing file. All steps of the build have the blue icon, but inside the build.xml I see only one line
  <result>FAILURE</result>
whereas the successful step had
    <hudson.tasks.Fingerprinter_-FingerprintAction>
      <record>
        <entry>
          <string>README.md</string>
          <string>3f7c3b7d5e5d582a09643416b80fafaf</string>
        </entry>
      </record>
    </hudson.tasks.Fingerprinter_-FingerprintAction>

[jenkins-infra-bot]

jglick:

• Original comment link
• Raw content of original comment:

  The ball color in Pipeline Steps for the last step does not reflect overall build status.
  

The ball color in Pipeline Steps for the last step does not reflect overall build status.

[jenkins-infra-bot]

svanoort:

• Original comment link
• Raw content of original comment:

  jglick Solved with the status APIs in pipeline-graph-analysis plugin (if a step is the last existing step in a run, build status overrides step status).   The logic there could be borrowed if cyclic dependencies would be a blocker. 
  

jglick Solved with the status APIs in pipeline-graph-analysis plugin (if a step is the last existing step in a run, build status overrides step status). The logic there could be borrowed if cyclic dependencies would be a blocker.