Closed
Bug 551520
Opened 15 years ago
Closed 15 years ago
need a staging server for hg.mozilla.org
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ted, Assigned: aravind)
References
Details
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.
Assignee | ||
Updated•15 years ago
|
Assignee: server-ops → aravind
Comment 1•15 years ago
|
||
This would also allow for load testing that doesn't affect hg.m.o =)
Assignee | ||
Comment 2•15 years ago
|
||
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
Closed: 15 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•