Community mailing list archives
RE: Runbot / Staging - argument's against madnessby
What are the benefits over the Runbot setup that Odoo currently has?
I think that the Runbot system just needs to be used better. Lots of commits seem to hit the master which break the builds (according to Runbot).
This should never happen.
From: David Arnold [mailto:firstname.lastname@example.org]
Sent: Friday, 2 January 2015 6:13 PM
Subject: Runbot / Staging - argument's against madness
Why Odoo doesn't rely on travis and simply pipe successfull runs to a staging server, like outlined here: http://docs.travis-ci.com/user/deployment/custom/
No, security is not the issue: http://docs.travis-ci.com/user/encryption-keys/
Deis (OpenSoruce PaaS), which could receive the travis pushes could even reside on your private laptop's CoreOS-VM: http://deis.io/overview/
(By the way, bite the bullet, it's coming anyway: DOCKER !!!)
- spending resources on maintaining code + configuration vs configuration-only
- using standard tools, versus writing documentation for self invented tools
- put the many arguments zipping through your head right now HERE.
Anyone capable of a proof-of-concept (probably with Deis on CoreOS-VM)? http://docs.travis-ci.com/user/deployment/deis/
David Arnold BA HSG / Analista
315 304 13 68/ email@example.com
devCO - empresa de consultoría de sistemas (en fundación)
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. devCO is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.