diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2017-03-28 16:18:53 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2017-03-28 16:18:53 +0200 |
| commit | 529211144b9b8a17bed3fbb4814f3349c1fe4bc4 (patch) | |
| tree | 97a9067e2768ee09985360094fa1303b60e912b1 /doc/manual.cli | |
| parent | 28b3d34d48146c47af3d29775832b094fb197acf (diff) | |
Minor documentation fixes
Diffstat (limited to 'doc/manual.cli')
| -rw-r--r-- | doc/manual.cli | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/doc/manual.cli b/doc/manual.cli index 9be688b..9138596 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -78,7 +78,7 @@ owner if the build failed. Similarly, a \c{bbot} controller that monitors a build failure. The email would include a link (normally HTTP/HTTPS) to the build logs hosted by the controller. -\h2#arch-machine-config|Configurations| +\h#arch-machine-config|Configurations| The \c{bbot} architecture distinguishes between a \i{machine configuration} and a \i{build configuration}. The machine configuration captures the @@ -152,10 +152,10 @@ a particular build configuration. For example: \ windows-vc_14-32-debug -linux-gcc-6-cross-arm-eabi +linux-gcc_6-cross-arm-eabi \ -\h2#arch-machine-manifest|Machine Manifest| +\h#arch-machine-manifest|Machine Manifest| \ SYNOPSIS @@ -200,7 +200,7 @@ manifests is also sent by \c{bbot} agents to controllers. || -\h2#arch-task-manifest|Task Manifest| +\h#arch-task-manifest|Task Manifest| \ SYNOPSIS @@ -253,7 +253,7 @@ build configuration to use for building the package. Additional build system configuration variables.|| -\h2#arch-result-manifest|Result Manifest| +\h#arch-result-manifest|Result Manifest| \ SYNOPSIS @@ -321,7 +321,7 @@ The result manifest describes a build result. last and in the same order as the corresponding \c{*-status} values.|| -\h2#arch-task-req-manifest|Task Request Manifest| +\h#arch-task-req-manifest|Task Request Manifest| \ SYNOPSIS @@ -346,7 +346,7 @@ starts with the task request manifest followed by a list of machine manifests. The SHA256 fingerprint of the agent's public key.|| -\h2#arch-task-res-manifest|Task Response Manifest| +\h#arch-task-res-manifest|Task Response Manifest| \ SYNOPSIS @@ -378,7 +378,7 @@ starts with the task request manifest followed by a list of machine manifests. the result.|| -\h2#arch-result-req-manifest|Result Request Manifest| +\h#arch-result-req-manifest|Result Request Manifest| \ SYNOPSIS @@ -405,7 +405,7 @@ only a successful but empty POST result is returned. task response.|| -\h2#arch-worker|Worker Logic| +\h#arch-worker|Worker Logic| The \c{bbot} worker builds each package in a \i{build environment} that is established for a particular build target. The environment has three @@ -465,7 +465,7 @@ fi exec \"$2\" --build \"$3\" cc config.c=gcc-6 \ -\h2#arch-controller|Controller Logic| +\h#arch-controller|Controller Logic| A \c{bbot} controller that issues own build tasks maps available build machines (as reported by agents) to \i{build configurations} according to the |