ReleaseEngineering/How To/Verify a New Taskcluster Platform: Difference between revisions

Revision as of 21:21, 10 April 2017

making sure api keys exist
making sure that the installer gets localized (on localized builds)
ensure google/etc api keys are in place
ensure information necessary [?] to let EME extensions load.
verify size of zip
verify package naming
verify package icons
Verify TC-dervied builds are byte-for-byte equivalent to buildbot builds#
manually sign build (manual-signed dmg, then task-signed, then full graph)
run talos (bug 1354804) and ensure that performance is on par with buildbot builds
run unit tests
Verify that the en-US+l10n nightlies and associated updated methods work via manual testing
verify updates work as expected - run update verify tests (Softvision QA can help)
Verify that the signature formats match those from buildbot builds

@@ Line 1: / Line 1: @@
 __TOC__
 {{Release Engineering How To|Verify_a_New_Taskcluster_Platform}}
+===General===
+# making sure api keys exist
+# making sure that the installer gets localized (on localized builds)
+# ensure google/etc api keys are in place
+# ensure information necessary [?] to let EME extensions load.
+# verify size of zip
+# verify package naming
+# verify package icons
+# Verify TC-dervied builds are byte-for-byte equivalent to buildbot builds#
+# manually sign build (manual-signed dmg, then task-signed, then full graph)
+# run talos (bug 1354804) and ensure that performance is on par with buildbot builds
+# run unit tests
+# Verify that the en-US+l10n nightlies and associated updated methods work via manual testing
+# verify updates work as expected - run update verify tests (Softvision QA can help)
+# Verify that the signature formats match those from buildbot builds
+===Platform Specific===
+* Macosx
+* Windows
+* Linux
+* Android