From f51a021dfe3fa4d70d6653f057f7e0403505ed6a Mon Sep 17 00:00:00 2001 From: Xavier-Do Date: Wed, 3 Jul 2019 13:50:31 +0200 Subject: [PATCH] [IMP] runbot: update repo in reversed order When updating repo, order is odoo/odoo, odoo-dev/odoo, odoo/enterprise, odoo-dev/enterprise The problem with this is that if a community hash and an enterprise hash arrives exactly between odoo/odoo and odoo/enterprise update, enterprise could have a newest version than community when creating builds. By inversing this order, we have less chances to have this cornercase (as unlikelly as it could be) --- runbot/models/repo.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/runbot/models/repo.py b/runbot/models/repo.py index d4e05d3b..cb1e7544 100644 --- a/runbot/models/repo.py +++ b/runbot/models/repo.py @@ -344,7 +344,7 @@ class runbot_repo(models.Model): @api.multi def _update(self, force=True): """ Update the physical git reposotories on FS""" - for repo in self: + for repo in reversed(self): try: repo._update_git(force) except Exception: