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.

I'm really glad for this question, as it points out a broader problem of the odoo ecosystem thinking.

And I would counter your question with the following:

What are the costs of not keeping pace with innovation?

As to your question, I would feel comfortable about responding and adhering to a general hermeneutic:

If a bunch of people do nothing else, than finding ways to improve CI for the teck flocks out there, and they earn their money with exactly this, chances are positive, that they end up to have a superior solution. Details are really too complex to discuss about without loosing focus ;) - but to name one: it is replicable for community development, with minimal overhead (register a travis token, that's all it needs) and another one is: probably programmers, that learned programming in university and not throughout the new odoo-api-dcumentaion might be very well feel quite comfortable to see tools like travis, instead of having to learn YET ANOTHER X :) - so the point here is talent attraction... you can ever go further down the line, and find as many arguments as you might want, runbot is going to loose almost in every single dispute point.

So what's the point of keeping it? I mean really...

We all know, that the Odoo world has a strong NIH problem, which probably is due to a lot of functional people which got in touch with programming through the odoo window (actually I'm such a case), but seeing that this is strategically bad is the first step in order to cure :)

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.

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.