Some of the answers on this site refer to 'runbot'.
Can you explain what this is and how I can use it?
8
13Answers
19
Best Answer
UPDATED JULY 2020: Update based on new runbot design
The Odoo Runbot (or simply runbot) is a server hosting installed editions/branches of Odoo.
It is available at http://runbot.odoo.com and is a constantly up to date server running Odoo for testing and demo purposes.
Several of the latest builds of the Odoo branches (11.0, 12,0. 13,0, saas 13.3 and 13.4 and master [to become v14]) as well as development and testing branches are available.
You log in with admin/admin.
There are generally two databases available 'all' (every module installed with demo data) and 'base' (no modules installed).
The home page of runbot shows green (# symbol) and red (# symbol) highlighted squares to indicate a build works (green) or doesn't work (red).
If you are having a problem with your Odoo installation, you can check if the same problem occurs on runbot (in which case it is probably a bug) or doesn't occur (in which case it is probably a configuration problem).
You can also use runbot to see what is different about a newer build than the one you have installed.
Bear in mind this is a multi-user environment. You may see evidence of others using the system at the same time you are using it.
For Odoo Partners, runbot is a platform where you can test the branches pushed on GitHub.
EDIT: (To address question about Continuous Integration)
Hover over any branch with a RED square (thumb down), and you will see a gear icon. Click it and select "Logs". You will then be able to see a detailed logfile indicating what failed.
Several logs indicating what happened during the build attempt will be available:
start with test-all.txt
Note: The Odoo Community Association has their own runbot server at https://runbot.odoo-community.org/runbot
7Comments
Hi Ray,
For CI, you would suggest using Runbot? The main drawback that I see in Runbot is that it runs all tests but does not tell me which is the test that fail. In a CI environment I would expect to see which are the tests that fails so I can go and fix them. But I think that this is not possible even when lunching OpenERP with test-enable right?
See my EDIT to my answer above.
Hi Ray, thanks for the reply. I know that this may be a detail but the log is quite verbose and finding where the error is and which is the test that fail is not easy.
I would have expected something like: <this> test fail. Where <this> is the name of the file and the module. This is how I saw most testings when programming in Java and other frameworks for example.
I think that this is not possible since OpenERP sever does not provider this information, am I right?
Can I upload my module to runbot and test it there? Where can I find some documentation about how to upload my module to test on runbot?
3rd and 4th sentences at the top of the Runbot page under ABOUT read: "If you are a partner, you should be able to register your team or branches from your Partner Portal. You can also grab a copy and run it yourself." Does that help?
That's exactly what I was looking for, thanks Ray!
Hi Ray,
Do you know where I could find information on writing tests for Odoo runbot?
1
Best Answer
Hello,
anyone know how to use odoo runbot in localhost ?
I get odoo runbot 13 in my localhost and I installe it but dont know how to use it !
any help with a tutorial please !
0
Best Answer
Please check the below link for more info about Odoo runbot:
http://odoo-development.readthedocs.io/en/latest/ci/runbot.html
0
Best Answer
RUnbot is tool on internet where you can try and test the latest or previous versions of Odoo
Where you can find the new changes in new APIs of odoo or enhancements as well.
WHere you can found that in which module have some bugs which module is in developing mode and fixing bugs.
2Comments
Don't suppose anyone can give the user name and password for the runbot? I tried admin/demo but no luck.
On login page enter credentials:
For Admin:
login: admin
password: admin
For Demo:
login: demo
password: demo
