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
Currently, if a downstream builder detects that the corresponding downstream commit was already built, it will fail with an error. Example failure
This means that if one downstream fails due to a transient error, it has to be resolved manually instead of by clicking "retry" on the failed cloudbuild. We should instead consider the downstream builds to be idempotent - if a particular commit has already made it to a downstream, we should consider that a success, since the desired end state has been achieved.
The text was updated successfully, but these errors were encountered:
I think this change should be fairly easy to make - a lot of the work here will be thinking through whether or not it's actually safe to do. We should also update the documentation around resolving this type of issue to reflect this change.
Currently, if a downstream builder detects that the corresponding downstream commit was already built, it will fail with an error. Example failure
This means that if one downstream fails due to a transient error, it has to be resolved manually instead of by clicking "retry" on the failed cloudbuild. We should instead consider the downstream builds to be idempotent - if a particular commit has already made it to a downstream, we should consider that a success, since the desired end state has been achieved.
The text was updated successfully, but these errors were encountered: