Closed
Bug 699007
Opened 13 years ago
Closed 13 years ago
Need different verify configs for beta and release channels (verify update steps fail on beta & release)
Categories
(Mozilla Messaging Graveyard :: Release Engineering, defect)
Mozilla Messaging Graveyard
Release Engineering
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: standard8, Assigned: standard8)
Details
Attachments
(2 files)
62.23 KB,
patch
|
gozer
:
review+
|
Details | Diff | Splinter Review |
2.46 KB,
patch
|
gozer
:
review+
|
Details | Diff | Splinter Review |
Currently we're using moz20-thunderbird-<platform>.cfg for our verify config files - for both Release & Beta channels. However, this is causing the <platform>_update_verify_<beta/release> runs to fail because the .cfg file contains information about builds on both beta and release channels, but each run is only testing one channel. Hence in the 8.0b4 run, it is complaining about the fact that 7.0 final isn't updated to 8.0b4, because it gets updated to 7.0.1 as that is correctly the only update for 7.0 that's been pushed to the beta channel. Firefox already have seperate config files, so we should do the same. Doing this will help us get better confidence in the update generation before QA gets to start testing them.
Assignee | ||
Comment 1•13 years ago
|
||
This should do the necessary work that we need.
Assignee | ||
Comment 2•13 years ago
|
||
These two patches should do what we need. I'm proposing we land them and then re-run the update verify for beta & release channels, which should then pass with these patches.
Attachment #575913 -
Flags: review?(gozer)
Updated•13 years ago
|
Attachment #575912 -
Flags: review?(gozer) → review+
Updated•13 years ago
|
Attachment #575913 -
Flags: review?(gozer) → review+
Assignee | ||
Comment 3•13 years ago
|
||
Checked in: http://hg.mozilla.org/build/buildbot-configs/rev/36ae97b4bf79 http://hg.mozilla.org/build/tools/rev/ad0db2342ce3 The changes are looking good so far on buildbot. Hopefully the next beta/release will be green :-)
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•