2. t @odony
A very special Continuous Integration tool
● Monitors Launchpad branches in real time
● Grabs a copy of each revision
● Constructs a valid set of branches per series
● Installs 2 databases – base / all
● Execute full test suite – YAML / Python
● Provide RED/GREEN output
● Keep live databases for a while
4. t @odony
A Critical Part of OpenERP Lifecycle
● Tests all bug fixes and improvements branches
● Validates all community contributions
● No branch merged when RED
● No nightly build, no SaaS deployment when RED
6. t @odony
Anatomy of proper branch names
lp:~mycompany-team/openobject-addons/7.0-bug-12345-me
Launchpad prefix lp: is an alias for bzr+ssh://bazaar.launchpad.net
Your team's unique Launchpad login
One of the core projects:
• openobject-addons
• openobject-server
• openerp-web (6.1 and up)
• openobject-client-web (for 6.0)
The branch name must start with a series: 6.0,
6.1, 7.0, or trunk
Branches that must be built together must have
the exact same name!
Pattern series-bug-number-... auto-links the bug
7. t @odony
Tips and tricks
● You can add a matching branch from another
project later, they will automatically rebuild
● You can Force Build a branch to make it live
again, when it has expired
● You can rename branches in Launchpad if
needed, Runbot ignores dead branches
● You can install modules on the base database
● Validating your branches with Runbot also
speeds up processing of your Merge Proposals!