Runbot

Introduction

Runbot automaticaly run test when a new commit is pushed in one of the observed repos. Its is strongly adviced to have basic github knowlege before using runbot.

Lexicon

• sticky branch: one of the main branch still maintained and displayed first on the runbot page.
• base branch: main branch, maintained or not. all sticky branches are abse branches.
• bundle: group of branches and pr related to the same project, linked by the branch name.
• batch: one execution of a bundle, a group of commit corresponding to the HEADs of all branches.
• build: a process that executes one or more step to execute the tests

Guidelines

Branch naming

• Branches should be suffixed with the user trigram.
• Branches pushed on github must be prefixed with the target branch name in order to help runbot to manage branches and pull requests the same way.
  • Good: 14.0-my-feature-tri, master-my-feature-tri
  • Bad: 14-my-feature-tri, my-feature-tri
• Branches with the same name in different repositories (odoo, enterprise, upgrade, design-theme) will be linked together. Don't push empty branches (HEAD matching main branch HEAD)
• When pushing new commit for the same bundle in multiple repositories, try to prepare all the commit and push them all at once (less than 60 second between each commit. See Batch creation)

Usage

The main page displays a summary of each bundles, one per line The left colum is the bundle name, other columns

Bundle

Batch

Batch creation

A new batch is created every time a new commit is pushed on one of the branch of the bundle. The batch is initailly in a preparing state, waiting for other commit on any branch of the bundle. Once 60 seconds are passed without any new commit, the batch creates or links the corresponding builds.

Batch slots

Each batch have slots for build entries as seen on the batch badge picture above. The 🔗 icon means that the build did not really happen in this batch but was linked to another in another batch instead. The reason is that a build with the same commit was executed before in another batch.

On the other hand, the #️⃣ icon means that a new commit hash was found and a build was executed in the batch.

The sign-in icon means that this build has a running Odoo instance and the icon can be clicked to log in.

Batch details

A batch page with more details can be reached from the batch by using the grey button in the upper left corner of the batch badge.

Also, a the batch page may contain useful warnings e.g. when one of the branch need to be rebased.

Build