Closed Bug 1242782 Opened 4 years ago Closed 4 years ago
release promotion mozharness l10n tasks should upload checksum and sigs
in production we expect checksums to be uploaded to candidates. looking at the most recent successful l10n job from release promotion, we are either not uploading the checksum and sig of checksum file or we are not creating those artifacts at all: e.g. what we expect in candidates: http://archive.mozilla.org/pub/firefox/candidates/44.0b2-candidates/build1/linux-i686/son/ e.g. what is uploaded to taskcluster: https://tools.taskcluster.net/task-inspector/#c62GKh_OQw-UqGWrwvkEEw/0
looks like post upload cmd is aware of the checksum artifacts so we are creating it: http://archive.mozilla.org/pub/firefox/tinderbox-builds/date-l10n/release-date_firefox_linux_l10n_repack-bm71-build1-build12.txt.gz 22:35:25 INFO - http://archive.mozilla.org/pub/firefox/nightly/latest-date-l10n/firefox-44.0.zh-TW.linux-i686.checksums.asc 22:35:25 INFO - http://archive.mozilla.org/pub/firefox/nightly/2015/12/2015-12-25-16-34-47-date-l10n/firefox-44.0.zh-TW.linux-i686.checksums.asc I suppose we just need to tell the "taskcluster-upload step" about it..
worked fine on date
Attachment #8723123 - Flags: review?(jlund)
Attachment #8723123 - Flags: review?(jlund) → review+
Comment on attachment 8723123 [details] [diff] [review] upload_l10n_checksums_sigs.diff https://hg.mozilla.org/integration/mozilla-inbound/rev/b9e59028b304
Attachment #8723123 - Flags: checked-in+
You need to log in before you can comment on or make changes to this bug.