Closed
Bug 462043
Opened 17 years ago
Closed 17 years ago
Write a BuildFactory containing all the necessary steps to do a test of bouncer links and compare the releasetest and release channel update snippets.
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
(Whiteboard: [hg-automation])
Attachments
(3 files, 1 obsolete file)
4.82 KB,
patch
|
nthomas
:
review+
|
Details | Diff | Splinter Review |
1.34 KB,
patch
|
nthomas
:
review+
|
Details | Diff | Splinter Review |
934 bytes,
patch
|
Details | Diff | Splinter Review |
Put simply, we should run our "Final Verification" test from Buildbot.
One note, when this goes to production I intend to make it runnable by linux and mac slaves (and win32 if I get around to testing on it).
Attachment #345150 -
Flags: review?(nthomas)
Assignee | ||
Updated•17 years ago
|
Whiteboard: [hg-automation]
Comment 1•17 years ago
|
||
Comment on attachment 345150 [details] [diff] [review]
[checked in] final verification, scriptified, buildbotified
>diff -r 3cfbcb8ac074 release/final-verification.sh
I look forward to the glorious day when all this stuff is in python.
>+cat $configs | grep -v major | sed 's/betatest/releasetest/' > update.cfg
Is the grep a leftover from testing ?
>+linuxUpdateVerifyConfig = 'moz191-firefox-linux.cfg'
>+macUpdateVerifyConfig = 'moz191-firefox-mac.cfg'
>+win32UpdateVerifyConfig = 'moz191-firefox-win32.cfg'
btw, do we have anything to bump these files in a mercurial world ? See BumpVerifyConfig in Bootstrap/Step/Updates.pm.
Attachment #345150 -
Flags: review?(nthomas) → review+
Assignee | ||
Comment 2•17 years ago
|
||
(In reply to comment #1)
> >+cat $configs | grep -v major | sed 's/betatest/releasetest/' > update.cfg
>
> Is the grep a leftover from testing ?
>
I kept it in because we'll want it there at some point going forward (granted, it's pretty far off). Come to think of it, we could probably add a BuildStep for this on 1.8/1.9 if we felt so inclined.
> >+linuxUpdateVerifyConfig = 'moz191-firefox-linux.cfg'
> >+macUpdateVerifyConfig = 'moz191-firefox-mac.cfg'
> >+win32UpdateVerifyConfig = 'moz191-firefox-win32.cfg'
>
> btw, do we have anything to bump these files in a mercurial world ? See
> BumpVerifyConfig in Bootstrap/Step/Updates.pm.
Not yet. Gonna pull that logic out RSN.
Assignee | ||
Comment 3•17 years ago
|
||
Comment on attachment 345150 [details] [diff] [review]
[checked in] final verification, scriptified, buildbotified
Checking in factory.py;
/cvsroot/mozilla/tools/buildbotcustom/process/factory.py,v <-- factory.py
new revision: 1.26; previous revision: 1.25
done
in buildbot-configs: changeset: 470:8e1e42f3be11
in hg-tools: changeset: 15:7477caabfe9e
Attachment #345150 -
Attachment description: final verification, scriptified, buildbotified → [checked in] final verification, scriptified, buildbotified
Assignee | ||
Updated•17 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 4•17 years ago
|
||
Nick, you're absolutely right about the | grep -v major, of course. I'll get a patch for that up soon.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 5•17 years ago
|
||
Attachment #345720 -
Flags: review?(nthomas)
Assignee | ||
Updated•17 years ago
|
Attachment #345720 -
Attachment is obsolete: true
Attachment #345720 -
Flags: review?(nthomas)
Assignee | ||
Comment 6•17 years ago
|
||
Comment on attachment 345720 [details] [diff] [review]
remove the | grep -v major
So, while working on bug 462145 I realized that the update verify script got imported into hg.m.o/build/tools. Once Bootstrap is updated to pull both l10nverify and update verify scripts from there we'll delete them from CVS. I should re-work this to pull from hg.m.o instead.
Assignee | ||
Comment 7•17 years ago
|
||
Alright....this greatly simplifies things. final-verification.sh lives alongside update verification scripts in hg.m.o/build/tools so we don't need to pull it from anywhere. Just create a new config, run it, and grep the log.
I uncovered an error case that wasn't previously handled (empty update.xml). This version handles that, too.
Attachment #345754 -
Flags: review?(nthomas)
Assignee | ||
Updated•17 years ago
|
Priority: -- → P2
Comment 8•17 years ago
|
||
Comment on attachment 345754 [details] [diff] [review]
[checked in] final verification, out of HG
Don't forget to update ReleaseFinalVerification in process/factory.py now that the cvsroot argument isn't needed. Nice catch on the error case.
Attachment #345754 -
Flags: review?(nthomas) → review+
Assignee | ||
Comment 9•17 years ago
|
||
Comment on attachment 345754 [details] [diff] [review]
[checked in] final verification, out of HG
changeset: 16:230fd143b7c1
Attachment #345754 -
Attachment description: final verification, out of HG → [checked in] final verification, out of HG
Assignee | ||
Comment 10•17 years ago
|
||
Checking in factory.py;
/cvsroot/mozilla/tools/buildbotcustom/process/factory.py,v <-- factory.py
new revision: 1.27; previous revision: 1.26
done
Assignee | ||
Updated•17 years ago
|
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•