Go to file
Christophe Monniez f50b13172d [FIX] runbot: ivalidate cache to get valid hook_time
When github reaches the hook controller, the repo hook_time field is
updated. That way, a git fetch is done only when the hook_time is newer
that the last fetch. If the hook_time is updated during the long running
cron that runs the _cron_fetch_and_schedule method, the hook_time is cached
and only the old hook time is seen until the cron's end. The cursor
commit is not enough. As a result, the new builds are scheduled in the
next cron run.

With this commit, the cache is invalidated after the commit, that way,
the hook_time field contains the correct value.
2019-03-15 08:08:22 +01:00
runbot [FIX] runbot: ivalidate cache to get valid hook_time 2019-03-15 08:08:22 +01:00
runbot_cla [IMP] runbot: add a job_type on branch and build 2019-01-22 14:18:58 +01:00
runbot_merge [IMP] runbot_merge: lock commit to update its status in hook 2019-03-11 14:54:58 +01:00
.gitignore [IMP] runbot smaller status bar 2015-01-18 19:21:32 +01:00
README.md [REF] README: update the readme file for the brand new repo 2018-03-08 16:59:39 +01:00

Odoo Runbot Repository

This repository contains the source code of Odoo testing bot runbot.odoo.com and related addons.

Runbot

The runbot/ directory holds the main runbot Odoo addon.

Runbot CLA addon

The runbot_cla/ directory contains an Odoo addon that checks CLA.