Closed Bug 420005 Opened 13 years ago Closed 13 years ago

update 1.8/1.9 release automation to test 2.0.0.13/3.0b5

Categories

(Release Engineering :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: rhelmer)

References

()

Details

Attachments

(3 files, 2 obsolete files)

Rolling these into the same bug, since it's a really similar task.

Now that we have binary Talkback packages, I think this'll be really easy on the 1.8 side. 

Depending on how this goes, we really should consider automatically syncing the cvsmirror from real CVS nightly automatically, and then we'd just need to bump the bootstrap.cfg in order to change what staging builds.
Depends on: 42005
Depends on: 417058
No longer depends on: 42005
Let's merge the staging masters first, now that staging is pretty stable.
Actually.. that has a dependency that's a little tricky, let's not block on 417058 after all.
No longer depends on: 417058
Summary: update 1.8/1.9 release automation to test 2.0.0.13/3.0b4 → update 1.8/1.9 release automation to test 2.0.0.13/3.0b5
Attached patch update staging to latest version (obsolete) — Splinter Review
Attachment #307521 - Flags: review?(nrthomas)
Whiteboard: waiting for review
Blocks: 401327
Priority: -- → P2
Comment on attachment 307521 [details] [diff] [review]
update staging to latest version

>Index: fx-moz18-nightly-staging-bootstrap.cfg
>===================================================================

Also need to update pullDate and l10n_pullDate ?

>Index: fx-moz19-staging-bootstrap.cfg
>===================================================================
>@@ -10,8 +10,8 @@
> l10n_pullDate   = 2008-01-07 09:00 PST

Same again.

>+oldVersion      = 3.0b4
>+oldRc           = 3

Only up to rc1 on 3.0b4, lets hope it stays that way ;-)

Otherwise r+
Attachment #307521 - Flags: review?(nrthomas) → review+
Comment on attachment 307521 [details] [diff] [review]
update staging to latest version

RCS file: /cvsroot/mozilla/tools/release/configs/fx-moz19-nightly-staging-bootstrap.cfg,v
done
Checking in fx-moz19-nightly-staging-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/fx-moz19-nightly-staging-bootstrap.cfg,v  <--  fx-moz19-nightly-staging-bootstrap.cfg
initial revision: 1.1
done
Checking in fx-moz19-staging-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/fx-moz19-staging-bootstrap.cfg,v  <--  fx-moz19-staging-bootstrap.cfg
new revision: 1.14; previous revision: 1.13
done
Checking in fx-moz18-nightly-staging-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/fx-moz18-nightly-staging-bootstrap.cfg,v  <--  fx-moz18-nightly-staging-bootstrap.cfg
new revision: 1.3; previous revision: 1.2
done
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
fx-moz19-staging-bootstrap.cfg contains:

version         = 3.0b3
milestone       = 1.9b3
# _RCn and _RELEASE will be appended as-needed
productTag      = FIREFOX_3_0b3
# Branch name and pull dates to use for base tag
branchTag       = HEAD
#RelbranchOverride = GECKO190_20071207_RELBRANCH
pullDate        = 2008-01-07 09:00 PST
l10n_pullDate   = 2008-01-07 09:00 PST
rc              = 1
# oldVersion and oldRc refer to the previous release
oldVersion      = 3.0b4
oldRc           = 3

Some problem with using 3.0b5 as in the attachment ? And you missed my comment about 3.0b4 not having an rc3.
Yeah sorry about that, itchy checkin finger!

Checking in fx-moz19-staging-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/fx-moz19-staging-bootstrap.cfg,v  <--  fx-moz19-staging-bootstrap.cfg
new revision: 1.15; previous revision: 1.14
done
Attachment #307521 - Attachment is obsolete: true
Staging still isn't back up 100%, reopening this until it is.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: waiting for review
We're stuck in this funny place between .13 and .14, so I noticed that the tag delete rule in the Makefile doesn't do the right thing.
Attachment #310151 - Flags: review?(bhearsum)
Comment on attachment 310151 [details] [diff] [review]
delete ${PRODUCT_TAG}_RELEASE on l10n repo, too

I think this is better done above the loop, right below 'cvs -d /builds/cvsmirror.clean/cvsroot rtag -d ${PRODUCT_TAG}_RELEASE mozilla'
Attachment #310151 - Flags: review?(bhearsum)
Good point, no reason to do this each time through the loop :)
Attachment #310151 - Attachment is obsolete: true
Attachment #310276 - Flags: review?(bhearsum)
Attachment #310276 - Flags: review?(bhearsum) → review+
Comment on attachment 310276 [details] [diff] [review]
[checked in] delete ${PRODUCT_TAG}_RELEASE on l10n repo take 2

Checking in Makefile;
/cvsroot/mozilla/tools/release/Makefile,v  <--  Makefile
new revision: 1.27; previous revision: 1.26
done
Attachment #310276 - Attachment description: delete ${PRODUCT_TAG}_RELEASE on l10n repo take 2 → [checked in] delete ${PRODUCT_TAG}_RELEASE on l10n repo take 2
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Also, 1.8 master no longer had "make stage" in it; re-add this.
Attachment #310826 - Flags: review?(bhearsum)
Landed patches in this bug as a bustage fix, and also updated the tools revision to UPDATE_PACKAGING_R3 in the bootstrap.cfg
Comment on attachment 310826 [details] [diff] [review]
oldRc should be 4, and "make stage" should honor it

landed this as a bustage fix.
Attachment #310826 - Flags: review?(bhearsum)
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.