зеркало из https://github.com/mozilla/gecko-dev.git
6adee62041
Chains a release-eme-free-repack-beetmover-checksums kind after release-eme-free-repack-beetmover, to move the target.checksums generated by the latter into the beetmover-checksums/ in candidates directory. Those are then consumed by release-generate-checksum kind. A lot of details like scopes, worker & provisioner, attributes, as well as data like repack_id and partner_path, are inherited directly from the parent beetmover task. Mainly to avoid recalculating them. In contrast to nightly builds, GPG signing of target.checksums has not been implemented. I don't believe that adds any value in our current system because the sigs are not verified. MozReview-Commit-ID: 38iz3J2PAXh --HG-- extra : rebase_source : 8f2bebe747d97437780f1bc0d9e2f42159aee8a6 |
||
---|---|---|
.. | ||
kind.yml |