Failed downstream jobs with # number fail to rebuild by upstream job that was manually triggered

[Asgarzadeh457]

Summary

Based on discussion 7518, I am unable to rebuild downstream jobs by manually triggering the upstream job

Steps to reproduce

I have pipeline A, B , C that are triggered by a launcher pipeline D upon its completion with SUCCESS
Trigger add to each pipleineJob section in Yaml file is :

pipelineJob('A') {
    triggers {
        upstream('D', 'SUCCESS')
    }
}

When pipeline A, B and C are marked SUCCESS or FAILED while associated with a build version (i.e v2023.x.x.x) , the automatic trigger via pipeline D works correctly
However, if downstream job fails and marked failed with build number # , the automatic trigger via pipeline D does not re-start build despite the SUCCESS status of pipeline D unless I manually rebuild downstream jobs separately

Type of error that caused the downstream job to fail in this case is a checkout failure to git repo

Expected results

When triggering pipeline D and upon completion with SUCCESS : downstream jobs A, B and C should be triggered and start build despite having failed before

Actual results

When triggering pipeline D and upon completion with SUCCESS : downstream jobs A, B and C are not triggered

Additional context

[Taylor Silva]

Is there a yaml pipeline you can share? From the discussion thread you linked there's plenty of examples there that you could probably use to help us build a reproducible case.

[Bernhard Schuster]

@taylorsilva https://ci.fff.rs/teams/main/pipelines/ci-tron-prs?vars.number=1 showcases a broken pipeline, where job foo was manually triggered, but downstream was never triggered, see drahnr/ci-tron#1 for the pipeline spec