Contributors mailing list archives
Re: runbot status update: we have dockerby
Virtualenv was the first option... But we can isolate the apt packages here.
A good example is https://github.com/OCA/delivery-carrier/pull/91
We need a particular version of a package.
Travis is green but runbot is red.
Then if we install that version of a package other repository could fail.
And we need explain to server admin (Alexander) why we need this version to install it manually.
This is not posible with virtualenv.
Then most used CI in the world is travis.
Are they using just virtualenv?
We saw that they are using docker.
Why they are using docker and work fine?
The main concept is VE (Virtual Environment) this is not a VM (Virtual Machine).
But the full post is here:
https://blog.travis-ci.com/2014-12-17-faster-builds-with-container-based-infrastructure/El 16/11/2016 2:38 a.m., "Laurent Mignon" <firstname.lastname@example.org> escribió:Thank you for this work but I'll never understand why we use docker since virtualenv exists...Thanks for all this huge works.2016-11-15 19:22 GMT+01:00 Pedro M. Baeza (Tecnativa) <email@example.com>:Thank you very much for summarizing them!Regards.@AlexanderThanks again.@PedroI can reply you with a small (very small) summarize:- Auto-ConfiguredOCA projects now are self-configured from github project using (1) MQT with meta-files like as:- .travis.yml (apt-get install)- requirements.txt (pip install)- oca_dependencies.txt (git clone)For runbot we need create a custom configuration to reproduce the same environment.- apt-get install- pip install manually- Configuration of repositories dependencies manually.Use runbot_travis2docker allow us use the same OCA projects self-configured in runbot and avoid create issue to install packages:- IsolatedBefore runbot use the same environment for all projects.Then if your project require the version of a package freeze and other one require other particular version is not posible because is the same environment.Using runbot_travis2docker you can use postgresql-9.5 or a custom freeze version of a packages because is isolated from other environments.Example:- Reproduce it locallyMany times we have a error in runbot or travis but we can't reproduce it in local.This environment allow us enforce the tools to reply a build in local with travis2docker (2)Examples:- Use of dockerUse docker open infinite possibles way to improvement the builds in the future:- @Jairo Yopis have good ideas about using concepts like as: serverless (More info with Jairo, please)- Use docker could allow us create a ssh connection to the build-instance isolated using our github.com/USER.keysThank you again for the hard work. Can you summarize the advantages of having this new architecture?Regards.Hello, Thanks to Moyses Lopez who fixed a small issue (caused by a local patch applied on our runbot), we now have dockerized builds working. I don't have enabled docker builds on all repositories for now, so you only get dockerized builds for: * rma * server-tools * web * website * account-financial-tools Please report any issue experienced on runbot builds on these projects. If everything seems fine, I'll do a real smoke test over a week end: reboot the servers to ensure that no builds are up, configure docker on all repositories and trigger a rebuild of all 8.0, 9.0 and 10.0 branches. Then I'll burn a candle in the nearby church and hope for the best... Still on my todo list: set up a weekly cron to run docker-gc. -- Alexandre Fayolle Chef de Projet Tel : +33 4 58 48 20 30 Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac Cedex http://www.camptocamp.com--