Closed
Bug 1354803
Opened 8 years ago
Closed 8 years ago
Validate Windows 2012 builds
Categories
(Firefox Build System :: Task Configuration, task)
Firefox Build System
Task Configuration
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: garndt, Unassigned)
References
Details
It does not appear that we have ever had a build validation done on the Windows 2012 builds produced within taskcluster to ensure that we can move forward with using and shipping these.
Comment 1•8 years ago
|
||
I'm looking for the steps we used to validate the Linux/Android builds but I wasn't involved in this process
so I don't have this information. Trying to create a list of steps to validate windows 2012 builds on tc to ensure they are shippable. Are there additional steps besides the one that I've thought off the top of my head
1) manually sign build
2) run talos (bug 1354804)
3) run unit tests
4) test updates
Flags: needinfo?(bugspam.Callek)
Comment 2•8 years ago
|
||
notes from #tcmigration
didn't we do something on date before we had builds signed automatically where we specified a manually signed artifact in a task?
3:07 PM I'm trying to figure out how to validate windows 2012 builds
3:07 PM on tc
3:09 PM
<aki> yeah, manual-signed dmg, then task-signed, then full graph
Comment 3•8 years ago
|
||
I started a list here that we can add too
https://wiki.mozilla.org/ReleaseEngineering/How_To/Verify_a_New_Taskcluster_Platform
Comment 4•8 years ago
|
||
Only thing I have to add is that I used diffoscope to try and find oddities (mostly with api keys, package naming etc)
See my android bug 1321005 where I also used diffoscope to try and pare down the diff size, (which was convoluted since its not fully geared for this use)
Also added to the doc itself, that we need to validate that sha's of extracted files match between zip, installer, and update, for windows.
Flags: needinfo?(bugspam.Callek)
Comment 5•8 years ago
|
||
I'm splitting this to multiple bugs,
tl;dr we validated the windows builds preliminarily, they are passing talos validation (not regressing) and some basic, rudimentary testing. Further testing in this way could be invalidated by the changes we make to enable them in the taskgraph and green up tests, so lets do more of that work then do the more in depth validation.
See-Also Bug 1357136 and Bug 1357139
Comment 6•8 years ago
|
||
Also: Bug 1357136
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: TaskCluster → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•