Closed Bug 1398805 Opened 7 years ago Closed 7 years ago

Add checksums builder in-tree

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P2)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: catlee, Assigned: mtabara)

References

Details

Attachments

(1 file)

Perhaps this gets done as part of beetmover work in bug 1332339?
If possible, let's converge on nightly - so support all checksum file types in both release+nightly.
Assignee: nobody → kmoir
Kim and I talked about how to tackle this last week. I'm having some seconds thoughts. I think it might be worth going with what Aki said in the first place. I think I can tweak beetmover to add those missing *.beet files so that we can reuse the existing script via BBB. This way we can tackle rewriting the checksums in the cleanup/future. I'm tweaking the beetmoverscript part to see if this is feasible. Will follow-up here with a PR.
Beetmoverscript is now updated to encompass checksums as well. It's slightly different than the old (mozharnes) beetmoverscript approach, but in a way similar. Idea is to: 1. Cocentrate all the checkscums information in form of .beet files under beetmover-checksums (e.g. [1]) 2. Enable BBB checksums builder (this will gather them all and build up the SHA256/512 SUMS + SUMMARY). 1) is done - see beetmover-checksums green builds from this graph[2]. Adding 2) will be slightly trickier as we need to make sure checksums is the last task to run in the graph. We'll need some dummy tasks there too + all the others as deps but other than that, should be good. [1]: http://ftp.stage.mozaws.net/pub/firefox/candidates/58.0b12-candidates/build6/beetmover-checksums/ [2]: https://tools.taskcluster.net/push-inspector/#/L-a-hZzMR4K_WvAQNXH4_A
Summary: Migrate checksums builder to TC → Add checksums builder in-tree
Stealing this off Kim's plate as I manage to have a look at it. Pushed part-1 https://hg.mozilla.org/projects/maple/rev/bfe8fd197a2e97eb3cbd40ad9e2b03e4b4493faf
Assignee: kmoir → mtabara
Asking for some feedback, in case I've missed something. Seems to work properly on my local graphs, I'll trigger a staging release to see how it behaves.
Attachment #8935509 - Flags: feedback?(aki)
Comment on attachment 8935509 [details] [diff] [review] Checksums builder Ship it [on maple] and test it :)
Attachment #8935509 - Flags: feedback?(aki) → feedback+
Attachment #8935509 - Attachment is patch: true
So the job[1] failed with some good logs[2]. Sounds like I accidentally moved the signature files (.asc) as well as .beet files which is obviously breaking one of the reading-content functions[3]. Solution is to simply keep .asc files as they are since they will be ignored by the checksums script[4]. [1]: https://tools.taskcluster.net/groups/bn9Ab9njQUugb5rKcemuvg/tasks/aVp3vGlARK2neAlMOJsHxw/details [2]: https://archive.mozilla.org/pub/firefox/tinderbox-builds/maple-noarch/release-maple-firefox_chcksms-bm71-build1-build0.txt.gz [3]: https://hg.mozilla.org/mozilla-central/file/tip/testing/mozharness/mozharness/mozilla/checksums.py#l6 [4]: https://hg.mozilla.org/mozilla-central/file/tip/testing/mozharness/scripts/release/generate-checksums.py#l216
http://ftp.stage.mozaws.net/pub/firefox/candidates/58.0b14-candidates/build5/ worked. Will add a trello card to make sure there are no missing (important) files in the checksums.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Everything looks as expected, except source file which is not included as it's not part of the beetmover-checksums chunk. We can add it later, but in the cleanup section, there's a trello card for that.
Status: RESOLVED → VERIFIED
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: