B2G/QA/BuildProccess: Difference between revisions

no edit summary
(Created page with "= Nightly Build Status = * please see https://wiki.mozilla.org/B2G/QA/Flame_OTA = Dogfood Build Status = * please see https://wiki.mozilla.org/B2G/QA/Spark = Processes for Sm...")
 
No edit summary
Line 46: Line 46:
* Dogfood failures may end up having the similar process.  Smoke test failures is higher priority.
* Dogfood failures may end up having the similar process.  Smoke test failures is higher priority.
* If a patch is made for an issue the following day and a new failure occurs, the tested build is patched with the new patch and a new build is kicked off and tested with the dogfood test suite.
* If a patch is made for an issue the following day and a new failure occurs, the tested build is patched with the new patch and a new build is kicked off and tested with the dogfood test suite.


== Challenges ==
== Challenges ==
Line 54: Line 53:
* more often than not, there can be multiple dogfood and smoke test failures that occur.
* more often than not, there can be multiple dogfood and smoke test failures that occur.
* Close monitoring of smoke test failures and pushing of backouts has not occurred since Bhavana (release manager) left
* Close monitoring of smoke test failures and pushing of backouts has not occurred since Bhavana (release manager) left
= T2M Base Builds =
* The occurrence of needing a new T2M Base build is when there has been a new gonk level change, that a new build is considered.
* T2M base builds follows a similar path as dogfood.
* When making a build, the img files are written over top of the original 18D base build
** https://github.com/nhirata/Nhirata_Scripts/blob/master/T2M_Flame.sh outlines what is done in the build.  Note: script doesn't run currently; It's probably better to fix/create a taskcluster script to kick off this build
* The build is sent to the TAM for T2M and they are asked to hosts the files
* Balrog will need to point to the FOTA build accordingly.
Confirmed users
4,378

edits