Xavier Morel 7659293a2b [IMP] runbot_merge: update staging timeout on 'pending' CI ... If the CI is greatly backed up (either insufficient capacity or jobs spike) a timeout which is normally perfectly fine might be insufficient e.g. given a 2h timeout, if a job normally takes 80mn but the staging's job starts 40mn after the staging was actually created we're sunk. And cancelling the staging once the job has finally gotten started is not going to improve load on the CI, it just wastes a CI slot. Therefore assume a `pending` event denotes the actual start of the job on the CI, and reset the timeout to start from that moment so ci_timeout is the timeout of the CI job itself, not of the staging having been created. Closes #202		2019-09-23 15:42:18 +02:00
..
__init__.py	[ADD] runbot_merge: a merge bot	2018-09-03 13:16:36 +02:00
pull_requests.py	[IMP] runbot_merge: update staging timeout on 'pending' CI	2019-09-23 15:42:18 +02:00
res_partner.py	[IMP] runbot_merge: don't quote signoff	2019-03-04 13:17:10 +01:00