zuul/zuul/driver/gerrit
Clark Boylan 6f125e56c6 Don't retry after Gerrit HTTP 409s
Gerrit will return an HTTP status 409 when you try to modify changes
that are already merged or abandoned. For example if you try to vote on
a change in these closed states. In those cases we don't actually want
to retry the request as doing so is a waste of effort.

Update the gerritconnection drive to handle HTTP 409s as a special case
that should not be retried.

Change-Id: I4bd7b8e5aa512bf0ba1d1bf7dd9a39c3843e6ff6
2020-04-27 17:46:53 -07:00
..
__init__.py Add support for the Gerrit checks plugin 2019-09-17 14:15:18 -07:00
auth.py Report to gerrit over HTTP 2018-07-26 16:43:07 -07:00
gcloudauth.py Add gcloud_service auth option for Gerrit driver 2020-01-30 08:09:00 -08:00
gerritconnection.py Don't retry after Gerrit HTTP 409s 2020-04-27 17:46:53 -07:00
gerritmodel.py Gerrit checks: trigger new patchset behavior 2020-02-13 14:00:33 -08:00
gerritreporter.py Support file comments via Github checks API 2020-02-19 14:01:41 +01:00
gerritsource.py Protect getCachedChanges from concurrent modification 2020-03-26 18:53:32 +01:00
gerrittrigger.py Add support for the Gerrit checks plugin 2019-09-17 14:15:18 -07:00