Talk:Deployments/Train

False expectations?

Greg, you added:

no window for automated tests before going to non-WP

As a reason to go against shortening our deployment cycle. Why? Master is always meant to be good to go - that's what being a continuous integration shop means (with the occasional, managed possibility of configuration / maintenance when new code paths are switched on). The automated tests should run from zuul as part of every single change before it's merged; that's the entire point of having automated tests… Jforrester (talk) 18:00, 11 May 2013 (UTC)

I know how it seems, on first glance, to not make sense. And, I COMPLETELY agree that "the automated tests should run from zuul as part of every single change before it's merged". Completely. But, the automated tests I was referring to in this "con" were the ones that run on production hosted test/test2 wikis. We sometimes find bugs on those wikis that we miss in BetaLabs/developer's laptops/our other CI stuff (eg: cloudbees). So, maybe I should clarify this as: "No window for automated tests against the production environment before going to all Non-Wikipedias". Greg Grossmeier (talk) 16:08, 13 May 2013 (UTC)

Cool. :-) Jforrester (talk) 17:19, 13 May 2013 (UTC)