]> git.ipfire.org Git - thirdparty/knot-resolver.git/commitdiff
ci/images/README: clarify usage of build.sh for Coverity Scan
authorOto Šťáva <oto.stava@nic.cz>
Mon, 8 Aug 2022 07:34:02 +0000 (09:34 +0200)
committerVladimír Čunát <vladimir.cunat@nic.cz>
Mon, 8 Aug 2022 09:40:35 +0000 (11:40 +0200)
ci/images/README.md

index 531c70c58d9e2979e6ff7398ff3256a1e3af32f6..0224960d00405acf5608c4836af36daff10f8b1e 100644 (file)
@@ -15,6 +15,14 @@ inputs for [Coverity Scan](https://scan.coverity.com/).
 It is used by the `coverity` CI job to generate and send data to Coverity Scan
 for analysis.
 
+To build this image, you need to retrieve the Coverity Scan token from the
+dashboard and pass it to the `build.sh` script using the `COVERITY_SCAN_TOKEN`
+environment variable, e.g.:
+
+```
+$ COVERITY_SCAN_TOKEN=the_secret_token ./build.sh debian-11-coverity
+```
+
 ### debian-bullseye
 
 Used to serve the same purpose as `debian-11`. As of 2022-03-09, it is still