Closed Bug 1380829 Opened 2 years ago Closed 2 years ago

Add binary transparency task to releasetasks

Categories

(Release Engineering :: Release Automation: Other, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: btang, Assigned: btang)

References

(Blocks 1 open bug)

Details

Attachments

(4 files, 2 obsolete files)

- Investigate templates (specifically checksums, as well as a taskcluster-native task) to learn about releasetasks and find definition differences
- Determine what to migrate over from manually configured binary transparency tasks
- Determine how to test generation of task graph locally
- Be able to run releasetasks tests locally
- Look at releasetask test files to understand the structure of releasetasks and its test structure
- Save a graph to file from a test for manual inspection
- Add a test for binary transparency
- added binary_transparency_enabled for mozilla-beta
Attachment #8889965 - Flags: review?(mtabara)
Attached patch bug1380829-tools-v1.diff (obsolete) — Splinter Review
- added binary_transparency_enabled to: release runner kwargs, (manual generative) release runner, and sanity kwargs checker
- also added into parameters of make_task_graph_strict_kwargs function
Attachment #8889967 - Flags: review?(mtabara)
Attached patch bug1380829-tools-v2.diff (obsolete) — Splinter Review
- updated binary_transparency_enabled in release-runner to default to False if it doesn't exist instead of hardcoding True
Attachment #8890083 - Flags: review?(mtabara)
Attachment #8889967 - Attachment is obsolete: true
Attachment #8889967 - Flags: review?(mtabara)
Attachment #8889965 - Flags: review?(mtabara) → review+
Attachment #8890083 - Flags: review?(mtabara) → review+
Hijacking this bug for a second to do a cleanup since we're here. Let's kill esr45 with fire!
Attachment #8890136 - Flags: review?(nthomas)
Comment on attachment 8890136 [details] [review]
Esr45 is dead, cleanup configs in releasetasks.

Approved by :nthomas in PR.
Attachment #8890136 - Flags: review?(nthomas) → review+
Attachment #8890083 - Attachment is obsolete: true
Attachment #8890572 - Flags: review+
Updated bm85's releaserunner from rev fbc86f515ef1 to f8a63f49524e, and restarted releaserunner.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
For some reason we didn't get a binary transparency task in the graph for 55.0b13, https://tools.taskcluster.net/groups/SCJmm1VGS4ip3XEQ-BaX0g, so we'll have to figure out why that is.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Ah, I should have done 'git pull' in bm85:~cltbld/releasetasks/ when deploying. Just updated from 06d13f5653c5be3ab4af3933e30da0911240ca06 to 546ea6d41045b78540884dff0961321c5fb4bf13.

Lets close this once we successfully generate a cert.
See Also: → 1385134
bug 1385134 plans a staging 56.0b1 we should enable BT on the staging branch (jamun). I expect the job will fail because of the hardcoded archive.m.o at https://github.com/mozilla-releng/releasetasks/blob/546ea6d41045b78540884dff0961321c5fb4bf13/releasetasks/templates/desktop/binary_transparency.yml.tmpl#L28. I think that's fine from the point of view of testing the graph generation and making sure the job runs.
Attachment #8891131 - Flags: review?(mtabara)
Comment on attachment 8891131 [details] [diff] [review]
[buildbot-configs] Enable binary transparency on jamun

Lgtm!
Attachment #8891131 - Flags: review?(mtabara) → review+
We had a staging release going on on Friday with this[1] graph. (central => jamun) I couldn't find binary transparency job there but:
a) there's lots of other tasks missing so I suspect there might be some misconfiguration somewhere
b) did we do a reconfig after https://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla/project_branches.py#l201 ? if not, should have we?

[1]: https://tools.taskcluster.net/push-inspector/#/d9RbMcpIS-2aRxImMKa8cA
Looks like I didn't deploy to the dev releaserunner for the changes here. So on bm83 I 
* updated ~cltbld/releasetasks/ from e9c41655ba706751c9e59528babeb2e94614bd1c to 546ea6d41045b78540884dff0961321c5fb4bf13
* updated /builds/releaserunner/tools from 077a4adc87dc to f686c083bf49  (to pick up f8a63f49524e from this bug)
* restarted releaserunner using supervisorctl

There is a 'checksums builder' task on d9RbMcpIS-2aRxImMKa8cA, so I'm hopeful that the next staging run will have a binary transparency worker.
The current staging release 56.0b1-build17 picked it up - the job is now created[1] \o/
Let's see how it goes.

[1]: https://tools.taskcluster.net/groups/PoPbnpb5Q1iRrbjmsFTV9A/tasks/_3z49ZMyTImqsY3rX6vkkg/details
Woo! It's failing in the expected way (see comment #14), so lets be positive and close this as FIXED again.
Status: REOPENED → RESOLVED
Closed: 2 years ago2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.