Pipeline X: * A -> * B (sync trigger) -> * C
Pipeline Y: `- D -> E (fails)
then people go to pipeline Y to find out what's wrong and often they try and use the Rebuild button. However clicking the Rebuild button kicks off a new instance of pipeline Y with the same parameters, but no connection to the build run in pipeline X, hence pipeline X won't go green by doing that.
The right way to get the whole run to green is to just retry step E, but that is not very obvious.
Is it possible to:
Either make the rebuild button on a sync triggered pipeline to replace the initial invocation from the parent with the new run
Or disable the rebuild button, so the only option is the step-retry.
When I have a pipeline that looks like this:
then people go to pipeline Y to find out what's wrong and often they try and use the
Rebuildbutton. However clicking theRebuildbutton kicks off a new instance of pipeline Y with the same parameters, but no connection to the build run in pipeline X, hence pipeline X won't go green by doing that. The right way to get the whole run to green is to just retry stepE, but that is not very obvious.Is it possible to:
loosely related to #467
cc @alextreppass