On 02/20/2013 12:04 PM, Luke Welling WMF wrote:
I am strongly of the opinion that within broad ranges deployment frequency
does not matter. It really does not matter if you deploy twice an hour or
every second day.
What teams deploy every second day?
But, having the machinery to make it so
On 02/20/2013 05:56 PM, Arthur Richards wrote:
Once we have MobileFrontend working properly (in a production-like manner)
on betalabs, we'll be a big step closer to this - particularly once
betalabs is continuously updating to head of master for MobileFrontend. I
believe a majority of the
On 02/20/2013 12:15 PM, Mark A. Hershberger wrote:
I think there is a lot of ground to cover before we get more
continuous deployments, but what were you thinking we needed?
A simpler and faster deployment process. The part of the process when
supervision is needed shouldn't, in my opinion,
- Original Message -
From: Juliusz Gonera jgon...@wikimedia.org
On 02/20/2013 12:04 PM, Luke Welling WMF wrote:
I am strongly of the opinion that within broad ranges deployment
frequency
does not matter. It really does not matter if you deploy twice an
hour or
every second
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
I am strongly of the opinion that within broad ranges deployment frequency
does not matter. It really does not matter if you deploy twice an hour or
every second day.
But, having the machinery to make it so that you could deploy twice an hour
if you wanted to is all kinds of valuable.
Putting
On 02/20/2013 02:04 PM, Juliusz Gonera wrote:
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.
Wikimedia is already doing deployments every other week. On top of
that, a wiki that gets a lot of use and is used
On Wed, Feb 20, 2013 at 12:04 PM, Juliusz Gonera jgon...@wikimedia.orgwrote:
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 don't know if this is true of other
On Wed, Feb 20, 2013 at 2:56 PM, Arthur Richards aricha...@wikimedia.orgwrote:
I know the QA team has been talking about coordinating automated testing
for mobile, but I'm not sure what the current status is - hopefully sooner
rather than later ;)
Everything is set up. The only missing piece
On Wed, Feb 20, 2013 at 4:12 PM, Željko Filipin zfili...@wikimedia.orgwrote:
On Wed, Feb 20, 2013 at 2:56 PM, Arthur Richards aricha...@wikimedia.org
wrote:
I know the QA team has been talking about coordinating automated testing
for mobile, but I'm not sure what the current status is -
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
On 26 December 2012 17:31, Chris McMahon cmcma...@wikimedia.org wrote:
Is it time to start such a discussion? Or is this premature?
Everyone has to first read and understand (possibly with shuddering)
https://twitter.com/DEVOPS_BORAT
- d.
___
Yes, I am seeking a Continuous Deployment solution for Limn. I would be
glad to participate in a centralization effort.
On Wed, Dec 26, 2012 at 12:38 PM, David Gerard dger...@gmail.com wrote:
On 26 December 2012 17:31, Chris McMahon cmcma...@wikimedia.org wrote:
Is it time to start such a
13 matches
Mail list logo
