Xavier Morel fa94b269de [FIX] runbot_merge: order of staging branch updates ... When creating staging branches from tmp, use the iteration order of the repos in the project (that way it's easy to see and eventually configure if we add sequences or whatever, in the short term it's the order in which the repos were added which is the one we want). This ensures we stage odoo/odoo before we stage odoo/enterprise without relying on dict order of iteration, or needing meta to be an OrderedDict. The issue is if stagings are created/updated the other way around, the runbot may pick up staging on odoo/enterprise before odoo/odoo has been updated, and thus build odoo/enterprise with the wrong odoo/odoo commit, and defeat the entire point of it. Example: http://runbot.odoo.com/runbot/build/376112 was triggered by the same staging as http://runbot.odoo.com/runbot/build/376113, but used the previous staging head. The creation order of tmp branches should not matter so ignore it.		2018-09-20 15:50:53 +02:00
..
__init__.py	[ADD] runbot_merge: a merge bot	2018-09-03 13:16:36 +02:00
pull_requests.py	[FIX] runbot_merge: order of staging branch updates	2018-09-20 15:50:53 +02:00
res_partner.py	[ADD] runbot_merge: a merge bot	2018-09-03 13:16:36 +02:00