runbot/runbot
Christophe Monniez c13128a229 [FIX] runbot: try to update github status multiple times
When updating github statuses, it happens that we face a "Bad gateway"
from github. In that case, the error is logged in the runbot logs and
that's it. As a consequence, when the runbot_merge is waiting status for
the staging branch and this kind of error occurs, the runbot_merge
timeouts and the users vainly search the reason.

With this commit, the runbot tries to update the status at least twice.
If it fails, an INFO message is logged on the build itself.
2019-06-19 10:20:38 +02:00
..
controllers [IMP] runbot: add optional warning message on frontend 2019-06-18 12:43:25 +02:00
data [IMP] runbot: add python3-markdown in Dockerfile 2019-06-18 11:50:48 +02:00
migrations [IMP] runbot: increase version and add migration scripts 2019-05-18 10:42:31 +02:00
models [FIX] runbot: try to update github status multiple times 2019-06-19 10:20:38 +02:00
security [FIX] runbot: various fixes (data improvement, python step, logs, ...) 2019-05-20 10:52:13 +02:00
static/src [IMP] runbot: exact rebuild 2019-06-18 12:42:07 +02:00
templates [FIX] runbot: kill children even if state is done 2019-06-18 13:33:45 +02:00
tests [FIX] runbot: try to update github status multiple times 2019-06-19 10:20:38 +02:00
views [IMP] runbot: add optional warning message on frontend 2019-06-18 12:43:25 +02:00
__init__.py [IMP] runbot: replace jobs by build configs 2019-05-18 10:42:31 +02:00
__manifest__.py [IMP] runbot: increase version and add migration scripts 2019-05-18 10:42:31 +02:00
common.py [IMP] runbot: add basic tests 2019-01-11 11:54:43 +01:00
container.py [IMP] runbot: replace jobs by build configs 2019-05-18 10:42:31 +02:00