add a macos test task to verify proper signing/notarization/stapling
Categories
(Release Engineering :: Release Automation, enhancement)
Tracking
(Not tracked)
People
(Reporter: jcristau, Unassigned)
Details
We recently broke stapling of firefox macos builds because we stopped including Contents/CodeResources in the notarization task's output artifact. We didn't catch that until it broke update-verify tasks in beta.
It would be nice if we could have a test task downstream of signing/notarization/stapling that checked that things can be verified properly.
Comment 1•2 years ago
|
||
(In reply to Julien Cristau [:jcristau] from comment #0)
We recently broke stapling of firefox macos builds because we stopped including Contents/CodeResources in the notarization task's output artifact. We didn't catch that until it broke update-verify tasks in beta.
It would be nice if we could have a test task downstream of signing/notarization/stapling that checked that things can be verified properly.
I wonder if we could do this as part of the existing startup-test tasks? (At the very least, this kind would has a good starting point for how to get things running in the right place/at the right times...)
Updated•7 months ago
|
Description
•