This will enable us to get rid of the Concourse retrys in developers pipelines. Remeber that developers added around 10 Concourse retrie around some steps i.e cogito put step. This was probably making the issue with rate limit even worse. On the other hand it was partially justified to not waste 1h build time just because of a transient github error while posting the status.
Real Concourse errors (worker disapered) are alredy handled by the Concourse itself, so after this is implemented we might be able to convince people to not use retry...
github: retry on status codes >= 500
This will enable us to get rid of the Concourse retrys in developers pipelines. Remeber that developers added around 10 Concourse retrie around some steps i.e cogito put step. This was probably making the issue with rate limit even worse. On the other hand it was partially justified to not waste 1h build time just because of a transient github error while posting the status.
Real Concourse errors (worker disapered) are alredy handled by the Concourse itself, so after this is implemented we might be able to convince people to not use retry...
Example: https://concourse-ci.org/attempts-step.html Example from Pix4D: https://github.com/Pix4D/pix4d-geospatial-desktop/blob/master/ci/pipelines/survey-template.yml#L7