Closed
Bug 466333
Opened 16 years ago
Closed 16 years ago
Nightly builds from mozilla-1.9.1 uploaded to wrong directories
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
References
Details
Attachments
(1 file)
613 bytes,
patch
|
nthomas
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
1, http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2008/11/2008-11-22-03-releases/mozilla-1.9.1/ instead of ...../2008/11/2008-11-22-03-mozilla-1.9.1/ 2, http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-releases/mozilla-1.9.1/ instead of ..../firefox/nightly/latest-mozilla1.9.1/ 3, symlink from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/mozilla-1.9.1/ to 2008/11/2008-11-22-03-releases/mozilla-1.9.1 MozillaStageUpload needs some help.
Assignee | ||
Comment 1•16 years ago
|
||
We use self.shortName elsewhere in the MercurialBuildFactory so this is just a consistency fix. Going to apply this to staging-master and verify it works.
Assignee: nobody → nthomas
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•16 years ago
|
||
Comment on attachment 349695 [details] [diff] [review] use shortName rather than branch Works fine in staging. Carrying bhearsum's r+ from IRC to land and deploy to production.
Attachment #349695 -
Flags: review+
Attachment #349695 -
Flags: checked‑in+
Assignee | ||
Comment 3•16 years ago
|
||
And fixed up the these dirs in firefox/nightly/2008/11/: 2008-11-23-18-mozilla-1.9.1 2008-11-23-03-mozilla-1.9.1 2008-11-23-02-mozilla-1.9.1 2008-11-22-03-mozilla-1.9.1 2008-11-22-02-mozilla-1.9.1 Leaving open for final verification.
Priority: -- → P2
Comment 4•16 years ago
|
||
Everything looks good today: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2008-11-24-02-mozilla-1.9.1/
Updated•16 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•