Release builds of XulRunner 2.0rc2 went to wrong place

RESOLVED FIXED

Status

Release Engineering
General
P2
normal
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: rail, Assigned: rail)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [releases][automation])

Attachments

(1 attachment)

They ended up in

ftp://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2.0-candidates/build2/

instead of

ftp://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2.0rc2-candidates/build2/

See also bug 642692
Only releaseConfig['milestone'] is used to define the version, which was '2.0' for this RC. As a result the files went to the same directory as RC1.

We need a variable to control directory names where we upload the files.

Updated

7 years ago
Priority: -- → P5
Assignee: nobody → rail
Priority: P5 → P2
Created attachment 545812 [details] [diff] [review]
use version

We should use version instead of milestone.
Attachment #545812 - Flags: review?(nrthomas)
Attachment #545812 - Flags: review?(nrthomas) → review+
Comment on attachment 545812 [details] [diff] [review]
use version

http://hg.mozilla.org/build/buildbotcustom/rev/bcf9b5c3e10b
Attachment #545812 - Flags: checked-in+
Preproduction release went fine.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
As long as Firefox and XULRunner versions stay in sync, this will work fine :)

Comment 6

7 years ago
Landed on production and reconfigured.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.