Talk:How to deploy code
Deploy to test2 first
- test2.wikipedia.org is basically a standard configuration wiki on the production cluster that we use as the final place for testing before going out to other production wikis. Pretty much anything destined for one of our top wikis or to a substantial number of smaller wikis should go to test2. That's especially true now that our QA team is relying on test2 as an automated test target.
- This guide focuses solely on how to get code live, assuming the deployer already knows what they want to accomplish. There should be more documentation about het deploy (maybe on this page, maybe on a separate page), and about deployment policy (ideally on a separate page linked from here). I think things like testwiki and test2wiki are better classified as deployment policy than actual deployment mechanics, and I think it would be useful to maintain some sense of separation there; this page is already quite large. --Catrope (talk) 13:46, 3 January 2013 (UTC)
Recommend "git rebase"?
As I understand it, you can do a plain "git rebase" in lieu of "git rebase origin/wmf/1.26wmf20", and it will have the same effect. If correct, this is a much safer command to recommend to deployers. It's too easy to accidentally rebase the wrong branch, and the outcome is disastrous. Should we change the recommendation? Awight (talk) 23:56, 2 September 2015 (UTC)
Common sense: how long to wait around?
In Fundraising Tech, we have a guideline that you *must* stick around for an hour after you finish deploying anything. If you can't wait around, don't deploy.
Should we suggest a concrete amount of time to wait around for fallout?
- There's How_to_deploy_code#Don't_leave_town right now which says "Ideally, stay online and in IRC channels like #wikimedia-tech and #wikimedia-operations for a couple of hours." We could change that to "ideally 2 hours, minimum 1 hour". Greg Grossmeier (talk) 21:46, 7 December 2017 (UTC)