Closed
Bug 616099
Opened 15 years ago
Closed 11 years ago
repo_setup should properly deal with shared hg clones
Categories
(Release Engineering :: Release Automation, defect, P4)
Release Engineering
Release Automation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Unassigned)
Details
(Whiteboard: [staging][automation])
During staging release test I hit a problem when repo_setup recreates users/stage-ffxbld repos, but local repo clones in /build/hg-shared stay untouched. This broke the at least l10n repacks with:
abort: unknown revision ...
Probably removing the corresponding shared repos for repo_setup would be enough.
Updated•15 years ago
|
Priority: -- → P4
Whiteboard: [staging] → [staging][automation]
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Updated•11 years ago
|
Component: Other → Release Automation
QA Contact: bhearsum
Comment 1•11 years ago
|
||
We killed this step awhile ago, and I'm pretty sure hgtool copes with this case better now anyways...
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•