Sorry for digging up an old thread, but today I also started wondering
if there's a way of making our deployments simpler and faster.
I'm not a big fan of special highly orchestrated events when the whole
team gathers and waits and then looks for regressions after deploying
dozens of commits at the same time. I've been reading a bit and it's a
fact that some projects do Continuous Deployment and it works for them:
http://radar.oreilly.com/2009/03/continuous-deployment-5-eas.html
http://timothyfitz.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/
http://www.slideshare.net/mikebrittain/mbrittain-continuous-deploymentalm3public
Is there any interest at WMF in taking this path at some point?
--
Juliusz
On 12/26/2012 09:31 AM, Chris McMahon wrote:
Hi,
A number of people I know of have ideas and aspirations pertaining to a
DevOps-style deployment process, a.k.a Continuous Deployment. In recent
times a number of pieces of such a system have become functional: Zuul,
Jenkins enhancements for tests, automated acceptance tests, etc.
But looking at mediawiki.org I don't see any sort of central discussion of
overall approach/design/process for DevOps/Continuous Deployment.
Is it time to start such a discussion? Or is this premature?
-Chris
_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
