Historically we've just taken Hg updates, as well as updates to our templates, hooks, and extensions directly on the production servers. This doesn't seem like a great idea, since we occasionally break stuff, and it impacts our build farm etc. We should get a staging setup so we can test new versions of Hg as well as updates to our customizations.
This would also allow for load testing that doesn't affect hg.m.o =)
Okay, hgstage.mozilla.org is now ready. I copied only the following repos to it. mozilla-central mozilla-build build/buildbot-configs build/tools users/tmielczarek_mozilla.com/stackwalk-net users/tmielczarek_mozilla.com/hg-bits users/aravind_mozilla.com/ppolicy You should be able to login to it via ssh and checkin code like the normal hg repo. Your LDAP username should work (like the normal hg repo). It has the same acls in place. You should also be able to add more user repos as you see fit the same was as we do in production (through the clone script). Its currently running hg 1.4. You can see the same problems with the templates that I saw when I deployed 1.4 to production repo. Please re-open the bug if you think I missed some part of it that makes it act unlike our main repo at hg.m.o.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.