Closed Bug 1213929 Opened 9 years ago Closed 9 years ago

Flame is not aliased to Flame-kk on B2G-mozilla-central-nightly-latest

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: nhirata, Assigned: catlee)

References

Details

1. go to B2G-mozilla-central-nightly-20151012030617 or B2G-mozilla-central-nightly-latest

Expected: flame aliased to flame-kk
Actual: flame has it's own build listed

Note: 
1. this causes the client not to default to the build that's being made by flame-kk; users will manually have to change the URL to 
https://aus4.mozilla.org/update/3/%PRODUCT%/%VERSION%/%BUILD_ID%/flame-kk/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
Flags: needinfo?(catlee)
Oh weird: B2G-mozilla-central-nightly-20151012030617 is set correctly with the flame aliased to flame-kk 
for some reason B2G-mozilla-central-nightly-latest is not set correctly: https://aus4-admin.mozilla.org/releases#B2G-mozilla-central-nightly-latest
I've fixed up the B2G-mozilla-central-nightly-latest blob to have flame aliased to flame-kk
Assignee: nobody → catlee
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(catlee)
Resolution: --- → FIXED
verified
Status: RESOLVED → VERIFIED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.