On Thu, Apr 10, 2014 at 2:57 PM, Bryan Davis <[email protected]> wrote: > TL;DR: The jenkins job [0] that pushes new code into deployment-prep > (beta) will be disabled on and off from 2014-04-10T21:00Z to > 2014-04-11T00:00Z.
The beta-code-update-eqiad is re-enabled and beta is getting regular code updates again. > The super evil long term plan here is to change the Jenkins job so > that it runs scap to push code to the apache hosts in beta. See bug > 63746 [1] for slightly more details. I'm happy to report that the evil plan is one step closer to fruition. I able to run scap manually on deployment-bastion. That actually took much less fiddling than I had imagined and I had time left over in my window to setup a Jenkins job [2] that will be running the scap process after each run of beta-code-update-eqiad/. This puts us really close to being able to say that scap is deploying the beta code. I want to watch the job run for a while without handholding and backport some manual changes into scap and puppet before moving on to the next steps. If things are stable I hope to make additional changes early/mid next week that will get the apaches in beta running from the scap shipped copies of MediaWiki rather than the NFS drive. > [0]: https://integration.wikimedia.org/ci/job/beta-code-update-eqiad > [1]: https://bugzilla.wikimedia.org/show_bug.cgi?id=63746 [2]: https://integration.wikimedia.org/ci/job/beta-scap-eqiad -- Bryan Davis Wikimedia Foundation <[email protected]> [[m:User:BDavis_(WMF)]] Sr Software Engineer Boise, ID USA irc: bd808 v:415.839.6885 x6855 _______________________________________________ QA mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/qa
