Tracking bug for Build and Release of TB2.0.0.14

RESOLVED FIXED

Status

defect
P2
normal
RESOLVED FIXED
11 years ago
6 years ago

People

(Reporter: nthomas, Assigned: nthomas)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(6 attachments)

Assignee

Updated

11 years ago
Status: NEW → ASSIGNED
Priority: -- → P1
Assignee

Comment 2

11 years ago
Comment on attachment 312810 [details] [diff] [review]
[checked in] bootstrap.cfg bump for rc1

Checking in tb-moz18-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/tb-moz18-bootstrap.cfg,v  <--  tb-moz18-bootstrap.cfg
new revision: 1.18; previous revision: 1.17
done

Needed to get going on RC1 so hoping for retrospective review.
Attachment #312810 - Attachment description: bootstrap.cfg bump for rc1 → [checked in] bootstrap.cfg bump for rc1
Assignee

Comment 3

11 years ago
This is because Tagging expects to find pre's in versions, and the right tags in client.mk.

Checking in client.mk;
/cvsroot/mozilla/client.mk,v  <--  client.mk
new revision: 1.245.2.40.4.2; previous revision: 1.245.2.40.4.1
done
Checking in config/milestone.txt;
/cvsroot/mozilla/config/milestone.txt,v  <--  milestone.txt
new revision: 3.27.2.22.4.2; previous revision: 3.27.2.22.4.1
done
Attachment #312817 - Flags: review?(rhelmer)
Assignee

Comment 4

11 years ago
Boxes were trying to push builds with:
 ssh -2 -i '/home/cltbld/.ssh/tbirdbld_dsa' -l cltbld production-1.8-master.build.mozilla.org
so the key and accounts don't match and it hangs at a password prompt.

Checked this in and moved the THUNDERBIRD_2_0_0_13_{RC1,RELEASE} tag on en-US, and THUNDERBIRD_2_0_0_13_{RC1,RELEASE}_l10n on l10n.
Attachment #312810 - Flags: review?(rhelmer) → review+
Attachment #312817 - Flags: review?(rhelmer) → review+
Assignee

Comment 5

11 years ago
Onto the backburner for now, needs to be scheduled after Fx 2.0.0.14.
Priority: P1 → P3
Updated summary, as we'll no longer be doing TB2.0.0.13.
Summary: Tracking bug for Build and Release of TB2.0.0.13 → Tracking bug for Build and Release of TB2.0.0.14
Assignee

Comment 7

11 years ago
Using this bug for 2.0.0.14 instead.
Assignee

Updated

11 years ago
Attachment #316242 - Attachment is patch: true
Attachment #316242 - Flags: review?(nrthomas)
Assignee

Comment 9

11 years ago
Comment on attachment 316242 [details] [diff] [review]
[checked in] bootstrap.cfg bump for 2.0.0.14 rc1

r+ and ...

Checking in tb-moz18-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/tb-moz18-bootstrap.cfg,v  <--  tb-moz18-bootstrap.cfg
new revision: 1.20; previous revision: 1.19
done
Attachment #316242 - Attachment description: bootstrap.cfg bump for 2.0.0.14 rc1 → [checked in] bootstrap.cfg bump for 2.0.0.14 rc1
Attachment #316242 - Flags: review?(nrthomas) → review+
Assignee

Comment 11

11 years ago
Comment on attachment 316263 [details] [diff] [review]
[checked in] module.ver, client.mk, version.txt and milestone.txt changes so that tagging finds what it's expecting

r+ and checked in:

Checking in client.mk;
/cvsroot/mozilla/client.mk,v  <--  client.mk
new revision: 1.245.2.40.4.6; previous revision: 1.245.2.40.4.5
done
Checking in config/milestone.txt;
/cvsroot/mozilla/config/milestone.txt,v  <--  milestone.txt
new revision: 3.27.2.22.4.6; previous revision: 3.27.2.22.4.5
done
Checking in mail/config/version.txt;
/cvsroot/mozilla/mail/config/version.txt,v  <--  version.txt
new revision: 1.4.4.17.4.2; previous revision: 1.4.4.17.4.1
done
Checking in mail/app/module.ver;
/cvsroot/mozilla/mail/app/module.ver,v  <--  module.ver
new revision: 1.7.2.19.4.2; previous revision: 1.7.2.19.4.1
done
Attachment #316263 - Attachment description: module.ver, client.mk, version.txt and milestone.txt changes so that tagging finds what it's expecting → [checked in] module.ver, client.mk, version.txt and milestone.txt changes so that tagging finds what it's expecting
Attachment #316263 - Flags: review?(nrthomas) → review+

Comment 12

11 years ago
There was a failure in the build (Source step) that was caused by updates to the tb-moz18-bootstrap.cfg to not use the master as a staging server.  Unfortunately, the Bootstrap code in use with tag RELEASE_AUTOMATION_M8_1 does not yet understand this configuration change.

This change needs to be backed out once the Thunderbird 2.0.0.14 build is complete.
Attachment #316463 - Flags: review?(nrthomas)
Assignee

Comment 13

11 years ago
Comment on attachment 316463 [details] [diff] [review]
[checked in] Config changes to backout the "not using master as staging".

r+ and ...

Checking in tb-moz18-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/tb-moz18-bootstrap.cfg,v  <--  tb-moz18-bootstrap.cfg
new revision: 1.21; previous revision: 1.20
done
Attachment #316463 - Attachment description: Config changes to backout the "not using master as staging". → [checked in] Config changes to backout the "not using master as staging".
Attachment #316463 - Flags: review?(nrthomas) → review+
Assignee

Updated

11 years ago
Priority: P3 → P2

Comment 14

11 years ago
There were problems during the Repack push on bm-xserve02 (mac) and cerberus-vm (windows).  I suspect they're minor, but I'm not sure.

bm-xserve02 reported:

 file has vanished: "/home/ftp/pub/thunderbird/nightly/2.0.0.14-candidates/rc1/.thunderbird-2.0.0.14.pa-IN.linux-i686.complete.mar.KwvZoP"


and cerberus-vm reported:

 rsync: link_stat "/data/cltbld/thunderbird-2.0.0.12/." failed: No such file or directory (2)
 rsync error: some files could not be transferred (code 23) at main.c(702)
Assignee

Comment 15

11 years ago
TB2.0.0.14 shipped yesterday. Since we already bumped the nightly version 2.0.0.15pre, this bug can get closed out.
Status: ASSIGNED → RESOLVED
Closed: 11 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.