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