View source | Discuss this page | Page history | Printable version   
Main Page
Upload file
What links here
Recent changes

PDF Books
Show collection (0 pages)
Collections help


ERP 2.50:TryServer



The try server is an easy way to test a branch or a patch without actually pushing the patch/branch into the core erp/devel/pi repository. Your code will go through the same tests as the main integration process. This allows you to run a simulated integration process, useful to guarantee that the real integration process remains healthy.

To use try server, you need to be a Openbravo ERP core developer with Mercurial push credentials in


To submit your commits to the try server:

hg push -f

And to see the results monitor the try tab in our build farm.

For convenience you can add the following lines to your $HOME/.hgrc:

try =

So sending your branch for testing will be as simple as:

hg push -f try


  1. A developer pushes a branch to the try repository.
  2. The try server will start running a series of tests, in the following order and rules:
    • Every block is run in parallel, so 2 jobs per block.
    • One block won't be run if the previous block is not successful. The exception is the try-api job, which checks if the API is broken or not. The rationale behind this is simple: in order to make this job succeed you would have to modify the api-checks repository, and this has to be done only when the commits reach erp/devel/pi. This try-api job, even if it fails, will help you plan your final push to erp/devel/pi.

Click on any of the jobs of the try tab to see a description of what it does.


There is one try server for all the developers. This means that sometimes you'll have to wait, and other times you'll be the first in the queue. It's a serial system. If you make a push, it enters into a queue, and once the jobs with higher priority finish (pushed before yours), your tests will start.


As long as your branch is related to erp/devel/pi you can use the try server. Just push your commits and it will just work.

Every time a developer pushes commits using hg push -f this creates a new head in the repository. This head becomes the tip of the repository. This is how this simple mechanism works.

TO-DO list

These are some pending features to be implemented:

Retrieved from ""

This page has been accessed 3,479 times. This page was last modified on 14 June 2011, at 11:04. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.