Closed
Bug 793520
Opened 12 years ago
Closed 12 years ago
Disable publishing on Try repository
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 725362
People
(Reporter: gps, Unassigned)
Details
Newer versions of Mercurial have a feature called "phases" (http://mercurial.selenic.com/wiki/Phases).
A behavior of phases is that when you push a changeset, Mercurial marks the changeset's phase as "public." Once a phase is public, Mercurial treats it as immutable. i.e. it is read-only. If you pushed a a patch from your patch queue, you can't even pop that patch!
This does not play well with Try. You push a try build and now all of a sudden every changeset in your patch queue is immutable. You have to manually go in and force reset the phase to non-public so Mercurial will let you modify things again.
Today, the workaround is to disable phase publishing on the client. In your hgrc, you add:
[phases]
publish = False
The downside is this disables phase publishing for all repos. This isn't terrific because phase publishing is actually useful for repos like mozilla-central.
As it turns out, you can disable publishing on the server side through the exact same mechanism! So, clients won't need to hack up their hgrc to disable phases. Instead, things will "just work."
This bug tracks disabling publishing/phases on the Try repository. You should just need to add the above config snippet to that repo's hgrc file. Once that's done, clients will publish to m-c, m-i, etc but not to Try and all will be happy.
I'm only asking for disabling on Try because that's the only repo I know about where this makes sense. If we have other repos with "throwaway" heads similar to Try, we should probably disable publishing there as well.
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Updated•10 years ago
|
Product: Release Engineering → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•