493451 - Get automated release harness to work for SeaMonkey

Status: RESOLVED FIXED

(SeaMonkey :: Release Engineering, defect)

Description

[Robert Kaiser]

The automated release harness created for Firefox in bug 433930 was designed with other apps like Thunderbird and SeaMonkey in mind, the next step after getting the new buildbot configs to work for SeaMonkey is to make use of this harness and get it hooked up for SeaMonkey releases.

Comment 1

[Robert Kaiser]

tag, source, linux_build, linux_repack, win32_build, win32_repack, macosx_build, macosx_repack steps work so far in testing, with ChatZilla excluded (not that easy to tag it just for testing and not influence normal code repos).

Open issues:
* ChatZilla testing
* "pretty names" (currently testing with them enabled, but we probably don't want them for SeaMonkey)
* hg/cvs account, see bug 496367
* signing (no plans or clue about that one)
* verification steps
* updates step (patcher configs, etc.)

Comment 2

[Robert Kaiser]

Attachment: baseline verify configs for SeaMonkey (checked in)

Those are the baseline verify configs for SeaMonkey, to be added to build/tools.

Comment 3

[Robert Kaiser]

Attachment: tools/patcher-configs/moz191-seamonkey-branch-patcher2.cfg (checked in)

This is the base patcher-config file for SeaMonkey that works with all my patches on dependent bugs.

Comment 4

[Robert Kaiser]

As a note, the open issues from comment #1 have all been cleared, we'll punt on signing for now and fake it and we'll be using pretty names, the whole harness works (only l10n_verify is untested as we don't have L10n for any previous release so it doesn't do a lot).

Comment 5

[[e-mail] (:bhearsum)]

Comment on attachment 385357 [details] [diff] [review]
baseline verify configs for SeaMonkey (checked in)

This should have 2.0a2 in it right now, actually. Because update_verify tests updating, it works from the second newest build (and the ones before that).

If you switch these to be all 2.0a2 information that should be OK. If you're going to be doing updates from 2.0a1 -> whatever you'll want to add that here, too.

When you spin 2.0a4 (or 2.0b1, or w/e) you can use the bumping script to bump these forward - it should add the 2.0a3 lines with all the necessary information (from, to, ftp_server, aus_server, etc.)

Comment 6

[[e-mail] (:bhearsum)]

Comment on attachment 385358 [details]
tools/patcher-configs/moz191-seamonkey-branch-patcher2.cfg (checked in)

>            <partial>
>                betatest-url   http://stage-old.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0a3-candidates/build2/update/%platform%/%locale%/seamonkey-2.0a2-2.0a3.partial.mar
>                path   seamonkey/nightly/2.0a3-candidates/build2/update/%platform%/%locale%/seamonkey-2.0a2-2.0a3.partial.mar
>                url   http://download.mozilla.org/?product=seamonkey-2.0a3-partial-2.0a2&os=%bouncer-platform%&lang=%locale%
>            </partial>

I don't see any partials for 2.0a2 -> a3. Unless they're hiding, or you're going to generate them later you should switch these paths/urls to be the same as the <complete> block.

The rest of this seems OK.

Comment 7

[[e-mail] (:bhearsum)]

Oh, I also noticed that there is some complete MARs hanging around in http://stage-old.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0a3-candidates/build2/update/ - is that intended?

Comment 8

[[e-mail] (:bhearsum)]

After chatting with KaiRo in IRC these are both fine. The patcher config points to partials that don't exist, which may be confusing if you ever look back on these, but the bump script will work fine with this config when you run b1.

The verify configs are fine for the first versions, I guess, keeping in mind that their entire contents will be replaced with correct 2.0a3 lines when you run b1.

Comment 9

[Robert Kaiser]

Comment on attachment 385357 [details] [diff] [review]
baseline verify configs for SeaMonkey (checked in)

Pushed the verify configs as http://hg.mozilla.org/build/tools/rev/2df9c53f7f11

Comment 10

[Robert Kaiser]

Comment on attachment 385358 [details]
tools/patcher-configs/moz191-seamonkey-branch-patcher2.cfg (checked in)

Checking in moz191-seamonkey-branch-patcher2.cfg;
/cvsroot/mozilla/tools/patcher-configs/moz191-seamonkey-branch-patcher2.cfg,v  <--  moz191-seamonkey-branch-patcher2.cfg
initial revision: 1.1
done

Comment 11

[Robert Kaiser]

The release harness itself worked nicely for 2.0b1 (with bug 504791 landed in a cloned repo I used there), just ran the final_verification step successfully.
Marking this bug fixed, bug 504791 has review, I just need to find time to do the checkin, probably after the release craziness is out of my mind.