You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 :
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
The text was updated successfully, but these errors were encountered:
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.
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 :
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
The text was updated successfully, but these errors were encountered: