Closed
Bug 1061700
Opened 10 years ago
Closed 3 years ago
merge_day/gecko_migration.py should be able to use from_revision
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: rail, Unassigned)
References
Details
(Whiteboard: [merge])
I tried to use a specific revision to migrate from aurora to beta by setting "from_repo_revision" in the config file. The changeset wasn't pointing to the tip of default. I hit a couple of issues. 1) tagging of aurora failed because the tagging commit was not on the tip of default. I tried to force it (force=True), but it was creating a new anon branch (default head). I tried to "hg up default" before running "hg tag", it worked but it needs more testing 2) "hg pull" pulls everything from mozilla-aurora regardless of revision, probably because of some manipulations of the revision passed to hg_pull() Also, http://hg.mozilla.org/build/mozharness/file/0006e28cddc5/scripts/merge_day/gecko_migration.py#l125 should look like: "revision": self.config.get("%s_repo_revision" % k, "default"),
Reporter | ||
Updated•10 years ago
|
Whiteboard: [merge]
Comment 1•3 years ago
|
||
This bug is from 7 years ago, old enough to reference aurora
.
We've automated merge day since then.
Let's close and open new for any other issues.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•