zuul/zuul/executor
Tobias Henkel c982bfed4d
Retry jobs failed with MERGER_FAILURE
We sometimes get failed jobs that failed with MERGER_FAILURE. This
error is misleading to the user because it actually doesn't indicate a
merge conflict but some infrastructure related error. We already have
various retry mechanisms in place that retry most of the possible
failure causes within the executor. But catching all these places we
need to retry is difficult so we should add a safety net and
reschedule jobs that failed with MERGER_FAILURE.

Change-Id: I8844b11850c0a2cd3faddb7d8e944750c9da78ea
2018-10-12 09:53:20 +02:00
..
sensors Support job pause 2018-08-09 10:07:34 +02:00
__init__.py Rename zuul-launcher to zuul-executor 2017-03-15 12:21:24 -04:00
client.py Retry jobs failed with MERGER_FAILURE 2018-10-12 09:53:20 +02:00
server.py Provide per-project ssh key to executor 2018-09-04 15:42:42 -07:00