Closed Bug 1558715 Opened 5 years ago Closed 5 years ago

Thunberbird 68.0b1 release: Beetmover moving files to wrong location

Categories

(Thunderbird :: Build Config, defect)

defect
Not set
normal

Tracking

(thunderbird68 affected, thunderbird69 unaffected)

RESOLVED FIXED
Thunderbird 68.0
Tracking Status
thunderbird68 --- affected
thunderbird69 --- unaffected

People

(Reporter: rjl, Assigned: rjl)

Details

Attachments

(7 files, 2 obsolete files)

During Thunderbird-68.0b1 promote phase, the Update Verify tasks all failed. The beetmover tasks read the wrong artifact map files and put things in the wrong place. (See attachment)

Attached patch beetmover-artifact_map.patch (obsolete) — Splinter Review
The new taskgraph shows that the correct artifact-map will get used:

```
"beetmover-repackage-linux64-shippable/opt": {
  "attributes": {
    "always_target": false,
    "artifact_map": "comm/taskcluster/comm_taskgraph/manifests/thunderbird_candidates.yml",
    "build_platform": "linux64-shippable",
    "build_type": "opt",
    "kind": "beetmover-repackage",
```

This only needs to go on beta, "by-release-type" should be okay on central.

Target Milestone: --- → Thunderbird 68.0
Version: unspecified → 68
Attachment #9071496 - Flags: review?(jorgk)
Comment on attachment 9071496 [details] [diff] [review]
beetmover-artifact_map.patch

OK. I wondered back in the days of uplifting this
https://hg.mozilla.org/releases/comm-beta/rev/002469441c43eec71db4fbc2eb4a1142c4ac7a35#l2.2
whether `by-release-type` wasn't too "modern" to work.

Any reason why you're reshuffling the order? default typically comes last, no, although it doesn't matter.
Attachment #9071496 - Flags: review?(jorgk) → review+
Comment on attachment 9071496 [details] [diff] [review]
beetmover-artifact_map.patch

Review of attachment 9071496 [details] [diff] [review]:
-----------------------------------------------------------------

::: taskcluster/ci/beetmover-checksums/kind.yml
@@ +22,5 @@
>          artifact_prefix: public
>          artifact_map:
> +            by-project:
> +                default: comm/taskcluster/comm_taskgraph/manifests/thunderbird_nightly.yml
> +                comm-(beta|esr60|esr68): comm/taskcluster/comm_taskgraph/manifests/thunderbird_candidates.yml

Actually, that's a copy/paste error, no? It was thunderbird_nightly_checksums.yml
Attachment #9071496 - Flags: review+
Attached patch Original patch with default last (obsolete) — Splinter Review
Attachment #9071496 - Attachment is obsolete: true
Attached patch Modified patchSplinter Review

Correcting the alleged copy/paste error. I'm not 100% sure, so I won't land this now.

Yes, it should be checksums.

(In reply to Jorg K (GMT+2) from comment #5)

Comment on attachment 9071496 [details] [diff] [review]
beetmover-artifact_map.patch
::: taskcluster/ci/beetmover-checksums/kind.yml
@@ +22,5 @@

     artifact_prefix: public
     artifact_map:
  •        by-project:
    
  •            default: comm/taskcluster/comm_taskgraph/manifests/thunderbird_nightly.yml
    
  •            comm-(beta|esr60|esr68): comm/taskcluster/comm_taskgraph/manifests/thunderbird_candidates.yml
    

Actually, that's a copy/paste error, no? It was
thunderbird_nightly_checksums.yml

Comment on attachment 9071545 [details] [diff] [review]
Original patch with default last

Marking as obsolete due to error pointed out in comment 5.
Attachment #9071545 - Attachment is obsolete: true

OK, I'm still playing with chat badges, and we have bug 1558778 / bug 1558790. So I'll land this later.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Will need uplift to beta.
Attachment #9071766 - Flags: review?(geoff)
Uplift to beta
Attachment #9071767 - Flags: review?(geoff)
Attachment #9071766 - Flags: review?(geoff) → review+
Attachment #9071767 - Flags: review?(geoff) → review+

Pushed by thunderbird@calypsoblue.org:
https://hg.mozilla.org/comm-central/rev/6c271e995e80
Followup: Remove bz2.mar file from artifact manifest. rs=bustage-fix
https://hg.mozilla.org/comm-central/rev/05fc0c90a102
Followup: Look for source checksums in public prefix. rs=bustage-fix

Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → FIXED

Some pedantic notes: If you have review, why not include it in the commit message, so r=darktrojan. Also, see picture ;-)

Reviewed output of mach taskgraph full to verify no more instances of
incorrect capitalization.
Attachment #9071949 - Flags: review?(jorgk)
Comment on attachment 9071949 [details] [diff] [review]
installer_capitalization.patch

Affecting the 68.0b1 release process.
Attachment #9071949 - Flags: approval-comm-beta?
Comment on attachment 9071949 [details] [diff] [review]
installer_capitalization.patch

Sigh, I messed that up when copying those files in a cloak-and-dagger operative under bustage-fix pressure :-(
Attachment #9071949 - Flags: review?(jorgk)
Attachment #9071949 - Flags: review+
Attachment #9071949 - Flags: approval-comm-beta?
Attachment #9071949 - Flags: approval-comm-beta+
Pushed by mozilla@jorgk.com:
https://hg.mozilla.org/comm-central/rev/eaeb15a4f683
Follow-up: Capitalize Win and Mac installer downloads. r=jorgk DONTBUILD
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: