diff options
| -rw-r--r-- | README.adoc | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/README.adoc b/README.adoc index b23f04b..f3aef45 100644 --- a/README.adoc +++ b/README.adoc | |||
| @@ -219,6 +219,19 @@ oe-selftest --run-tests updater | |||
| 219 | 219 | ||
| 220 | For more information about oe-selftest, including details about how to run individual test modules or classes, please refer to the https://wiki.yoctoproject.org/wiki/Oe-selftest[Yocto Project wiki]. | 220 | For more information about oe-selftest, including details about how to run individual test modules or classes, please refer to the https://wiki.yoctoproject.org/wiki/Oe-selftest[Yocto Project wiki]. |
| 221 | 221 | ||
| 222 | == Aktualizr test suite with ptest | ||
| 223 | |||
| 224 | The meta-updater layer includes support for running parts of the aktualizr test suite on deployed devices through link:https://wiki.yoctoproject.org/wiki/Ptest[Yocto's ptest functionality]. Since it adds significant build time cost, it is currently disabled by default. To enable it, add the following to your `conf/local.conf`: | ||
| 225 | |||
| 226 | ``` | ||
| 227 | PTEST_ENABLED_pn-aktualizr = "1" | ||
| 228 | IMAGE_INSTALL_append += " aktualizr-ptest ptest-runner " | ||
| 229 | ``` | ||
| 230 | |||
| 231 | Be aware that it will add several hundreds of MB to the generated file system. | ||
| 232 | |||
| 233 | The aktualizr tests will now be part of the deployed ptest suite, which can be run by calling `ptest-runner`. Alternatively, the required files and run script can be found in `/usr/lib/aktualizr/ptest`. | ||
| 234 | |||
| 222 | == Manual provisoning | 235 | == Manual provisoning |
| 223 | 236 | ||
| 224 | As described in <<sota-related-variables-in-localconf,SOTA-related variables in local.conf>> section you can set `SOTA_DEPLOY_CREDENTIALS` to `0` to prevent deploying credentials to the built `wic` image. In this case you get a generic image that you can use e.g. on a production line to flash a series of devices. The cost of this approach is that this image is half-baked and should be provisioned before it can connect to the backend. | 237 | As described in <<sota-related-variables-in-localconf,SOTA-related variables in local.conf>> section you can set `SOTA_DEPLOY_CREDENTIALS` to `0` to prevent deploying credentials to the built `wic` image. In this case you get a generic image that you can use e.g. on a production line to flash a series of devices. The cost of this approach is that this image is half-baked and should be provisioned before it can connect to the backend. |
