diff options
Diffstat (limited to 'documentation/test-manual/test-manual-test-process.rst')
| -rw-r--r-- | documentation/test-manual/test-manual-test-process.rst | 14 |
1 files changed, 6 insertions, 8 deletions
diff --git a/documentation/test-manual/test-manual-test-process.rst b/documentation/test-manual/test-manual-test-process.rst index df825f8efa..96e71bf314 100644 --- a/documentation/test-manual/test-manual-test-process.rst +++ b/documentation/test-manual/test-manual-test-process.rst | |||
| @@ -23,11 +23,11 @@ We have two broad categories of test builds, including "full" and | |||
| 23 | "quick". On the Autobuilder, these can be seen as "a-quick" and | 23 | "quick". On the Autobuilder, these can be seen as "a-quick" and |
| 24 | "a-full", simply for ease of sorting in the UI. Use our Autobuilder | 24 | "a-full", simply for ease of sorting in the UI. Use our Autobuilder |
| 25 | console view to see where me manage most test-related items, available | 25 | console view to see where me manage most test-related items, available |
| 26 | at: `https://autobuilder.yoctoproject.org/typhoon/#/console <#>`__. | 26 | at: :yocto_ab:`/typhoon/#/console`. |
| 27 | 27 | ||
| 28 | Builds are triggered manually when the test branches are ready. The | 28 | Builds are triggered manually when the test branches are ready. The |
| 29 | builds are monitored by the SWAT team. For additional information, see | 29 | builds are monitored by the SWAT team. For additional information, see |
| 30 | `https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team <#>`__. | 30 | :yocto_wiki:`/wiki/Yocto_Build_Failure_Swat_Team`. |
| 31 | If successful, the changes would usually be merged to the ``master`` | 31 | If successful, the changes would usually be merged to the ``master`` |
| 32 | branch. If not successful, someone would respond to the changes on the | 32 | branch. If not successful, someone would respond to the changes on the |
| 33 | mailing list explaining that there was a failure in testing. The choice | 33 | mailing list explaining that there was a failure in testing. The choice |
| @@ -37,9 +37,9 @@ which the result was required. | |||
| 37 | The Autobuilder does build the ``master`` branch once daily for several | 37 | The Autobuilder does build the ``master`` branch once daily for several |
| 38 | reasons, in particular, to ensure the current ``master`` branch does | 38 | reasons, in particular, to ensure the current ``master`` branch does |
| 39 | build, but also to keep ``yocto-testresults`` | 39 | build, but also to keep ``yocto-testresults`` |
| 40 | (`http://git.yoctoproject.org/cgit.cgi/yocto-testresults/ <#>`__), | 40 | (:yocto_git:`/cgit.cgi/yocto-testresults/`), |
| 41 | buildhistory | 41 | buildhistory |
| 42 | (`http://git.yoctoproject.org/cgit.cgi/poky-buildhistory/ <#>`__), and | 42 | (:yocto_git:`/cgit.cgi/poky-buildhistory/`), and |
| 43 | our sstate up to date. On the weekend, there is a master-next build | 43 | our sstate up to date. On the weekend, there is a master-next build |
| 44 | instead to ensure the test results are updated for the less frequently | 44 | instead to ensure the test results are updated for the less frequently |
| 45 | run targets. | 45 | run targets. |
| @@ -47,7 +47,7 @@ run targets. | |||
| 47 | Performance builds (buildperf-\* targets in the console) are triggered | 47 | Performance builds (buildperf-\* targets in the console) are triggered |
| 48 | separately every six hours and automatically push their results to the | 48 | separately every six hours and automatically push their results to the |
| 49 | buildstats repository at: | 49 | buildstats repository at: |
| 50 | `http://git.yoctoproject.org/cgit.cgi/yocto-buildstats/ <#>`__. | 50 | :yocto_git:`/cgit.cgi/yocto-buildstats/`. |
| 51 | 51 | ||
| 52 | The 'quick' targets have been selected to be the ones which catch the | 52 | The 'quick' targets have been selected to be the ones which catch the |
| 53 | most failures or give the most valuable data. We run 'fast' ptests in | 53 | most failures or give the most valuable data. We run 'fast' ptests in |
| @@ -56,8 +56,6 @@ target doesn't include \*-lsb builds for all architectures, some world | |||
| 56 | builds and doesn't trigger performance tests or ltp testing. The full | 56 | builds and doesn't trigger performance tests or ltp testing. The full |
| 57 | build includes all these things and is slower but more comprehensive. | 57 | build includes all these things and is slower but more comprehensive. |
| 58 | 58 | ||
| 59 | .. _test-yocto-project-autobuilder-overview: | ||
| 60 | |||
| 61 | Release Builds | 59 | Release Builds |
| 62 | ============== | 60 | ============== |
| 63 | 61 | ||
| @@ -76,7 +74,7 @@ box to "generate an email to QA"is also checked. | |||
| 76 | When the build completes, an email is sent out using the send-qa-email | 74 | When the build completes, an email is sent out using the send-qa-email |
| 77 | script in the ``yocto-autobuilder-helper`` repository to the list of | 75 | script in the ``yocto-autobuilder-helper`` repository to the list of |
| 78 | people configured for that release. Release builds are placed into a | 76 | people configured for that release. Release builds are placed into a |
| 79 | directory in `https://autobuilder.yocto.io/pub/releases <#>`__ on the | 77 | directory in https://autobuilder.yocto.io/pub/releases on the |
| 80 | Autobuilder which is included in the email. The process from here is | 78 | Autobuilder which is included in the email. The process from here is |
| 81 | more manual and control is effectively passed to release engineering. | 79 | more manual and control is effectively passed to release engineering. |
| 82 | The next steps include: | 80 | The next steps include: |