Open
Bug 1340242
Opened 7 years ago
Updated 10 months ago
Develop build comparison tools
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
NEW
People
(Reporter: catlee, Unassigned)
Details
We need well maintained and reliable ways of comparing and verifying various build artifacts from automation. Some known use cases: * Verify signatures (MAR, EXE, DMG, GPG, etc.) are valid * Compare unsigned artifacts to signed artifacts to ensure that the only change is the signature * Compare localized builds to unlocalized builds to ensure that only strings have changed * Compare two builds on the same platform from the same revision and same buildid and make sure that the generated binaries are equivalent * Compare two packages from the same build (e.g. installer EXE and complete MAR) and make sure that both contain the same binaries Some of these comparisons will need to cope with known non-determinism in our build/release processes such as .chk files, timestamps in signatures, etc. These exceptions should be clearly defined and inspectable in the comparison tool. These kinds of comparisons are useful for auditing our processes, but also for verifying changes that we ourselves make.
Assignee | ||
Updated•7 years ago
|
Component: Tools → General
Reporter | ||
Updated•7 years ago
|
Priority: -- → P3
Updated•10 months ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•