diff options
Diffstat (limited to 'documentation/test-manual/test-manual-understand-autobuilder.rst')
-rw-r--r-- | documentation/test-manual/test-manual-understand-autobuilder.rst | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/documentation/test-manual/test-manual-understand-autobuilder.rst b/documentation/test-manual/test-manual-understand-autobuilder.rst index 0809190b5b..2fcae5000e 100644 --- a/documentation/test-manual/test-manual-understand-autobuilder.rst +++ b/documentation/test-manual/test-manual-understand-autobuilder.rst | |||
@@ -7,19 +7,19 @@ Understanding the Yocto Project Autobuilder | |||
7 | Execution Flow within the Autobuilder | 7 | Execution Flow within the Autobuilder |
8 | ===================================== | 8 | ===================================== |
9 | 9 | ||
10 | The “a-full” and “a-quick” targets are the usual entry points into the | 10 | The "a-full" and "a-quick" targets are the usual entry points into the |
11 | Autobuilder and it makes sense to follow the process through the system | 11 | Autobuilder and it makes sense to follow the process through the system |
12 | starting there. This is best visualised from the Autobuilder Console | 12 | starting there. This is best visualised from the Autobuilder Console |
13 | view (:yocto_ab:`/typhoon/#/console`). | 13 | view (:yocto_ab:`/typhoon/#/console`). |
14 | 14 | ||
15 | Each item along the top of that view represents some “target build” and | 15 | Each item along the top of that view represents some "target build" and |
16 | these targets are all run in parallel. The ‘full’ build will trigger the | 16 | these targets are all run in parallel. The 'full' build will trigger the |
17 | majority of them, the “quick” build will trigger some subset of them. | 17 | majority of them, the "quick" build will trigger some subset of them. |
18 | The Autobuilder effectively runs whichever configuration is defined for | 18 | The Autobuilder effectively runs whichever configuration is defined for |
19 | each of those targets on a seperate buildbot worker. To understand the | 19 | each of those targets on a seperate buildbot worker. To understand the |
20 | configuration, you need to look at the entry on ``config.json`` file | 20 | configuration, you need to look at the entry on ``config.json`` file |
21 | within the ``yocto-autobuilder-helper`` repository. The targets are | 21 | within the ``yocto-autobuilder-helper`` repository. The targets are |
22 | defined in the ‘overrides’ section, a quick example could be qemux86-64 | 22 | defined in the ‘overrides' section, a quick example could be qemux86-64 |
23 | which looks like:: | 23 | which looks like:: |
24 | 24 | ||
25 | "qemux86-64" : { | 25 | "qemux86-64" : { |
@@ -32,8 +32,8 @@ which looks like:: | |||
32 | } | 32 | } |
33 | }, | 33 | }, |
34 | 34 | ||
35 | And to expand that, you need the “arch-qemu” entry from | 35 | And to expand that, you need the "arch-qemu" entry from |
36 | the “templates” section, which looks like:: | 36 | the "templates" section, which looks like:: |
37 | 37 | ||
38 | "arch-qemu" : { | 38 | "arch-qemu" : { |
39 | "BUILDINFO" : true, | 39 | "BUILDINFO" : true, |
@@ -54,9 +54,9 @@ the “templates” section, which looks like:: | |||
54 | } | 54 | } |
55 | }, | 55 | }, |
56 | 56 | ||
57 | Combining these two entries you can see that “qemux86-64” is a three step build where the | 57 | Combining these two entries you can see that "qemux86-64" is a three step build where the |
58 | ``bitbake BBTARGETS`` would be run, then ``bitbake SANITYTARGETS`` for each step; all for | 58 | ``bitbake BBTARGETS`` would be run, then ``bitbake SANITYTARGETS`` for each step; all for |
59 | ``MACHINE=”qemx86-64”`` but with differing SDKMACHINE settings. In step | 59 | ``MACHINE="qemx86-64"`` but with differing SDKMACHINE settings. In step |
60 | 1 an extra variable is added to the ``auto.conf`` file to enable wic | 60 | 1 an extra variable is added to the ``auto.conf`` file to enable wic |
61 | image generation. | 61 | image generation. |
62 | 62 | ||
@@ -262,7 +262,7 @@ of post-build steps, including: | |||
262 | 262 | ||
263 | #. Cleanup the build directory using | 263 | #. Cleanup the build directory using |
264 | :ref:`test-manual/test-manual-understand-autobuilder:clobberdir` if the build was successful, | 264 | :ref:`test-manual/test-manual-understand-autobuilder:clobberdir` if the build was successful, |
265 | else rename it to “build-renamed” for potential future debugging. | 265 | else rename it to "build-renamed" for potential future debugging. |
266 | 266 | ||
267 | .. _test-deploying-yp-autobuilder: | 267 | .. _test-deploying-yp-autobuilder: |
268 | 268 | ||