Xavier Morel 78cc8835ce [IMP] rubnbot_merge: avoid triggering every cron on every test ... Since every cron runs on a fresh database, on the first `run_crons` every single cron in the db will run even though almost none of them is relevant. Aside from the slight inefficiency, this creates unnecessary extra garbage in the test logs. By setting the `nextcall` of all crons to infinity in the template we avoid this issue, only triggered crons (or the crons whose nextcall we set ourselves) will trigger during calls. This requires adjusting the branch cleanup cron slightly: it didn't correctly handle the initial run (`lastcall` being false).		2024-08-05 08:03:56 +02:00
..
__init__.py	[ADD] runbot_merge: delete scratch branches when a branch is disabled	2023-08-31 09:07:01 +02:00
cleanup_scratch_branches.py	[IMP] rubnbot_merge: avoid triggering every cron on every test	2024-08-05 08:03:56 +02:00
cleanup_scratch_branches.xml	[ADD] runbot_merge: delete scratch branches when a branch is disabled	2023-08-31 09:07:01 +02:00
git_maintenance.py	[CHG] forwardport: perform forward porting without working copies	2024-07-08 14:37:14 +02:00
git_maintenance.xml	[CHG] *: move repo cache from forwardbot to mergebot	2023-08-25 15:04:48 +02:00