diff options
| author | Paolo Bonzini | 2020-04-22 16:38:57 +0200 |
|---|---|---|
| committer | Paolo Bonzini | 2020-06-10 18:09:34 +0200 |
| commit | fbb84f074174aa3bb6fde4a63b569a1f7e64f264 (patch) | |
| tree | 52956f9fe3d2e79b9f0903ab6d43cda1c50b3cc8 /dump | |
| parent | run-coverity-scan: download tools outside the container (diff) | |
| download | qemu-fbb84f074174aa3bb6fde4a63b569a1f7e64f264.tar.gz qemu-fbb84f074174aa3bb6fde4a63b569a1f7e64f264.tar.xz qemu-fbb84f074174aa3bb6fde4a63b569a1f7e64f264.zip | |
run-coverity-scan: support --update-tools-only --docker
Just build the container when run-coverity-scan is invoked with
--update-tools-only --docker. This requires moving the "docker build"
logic into the update_coverity_tools function.
The only snag is that --update-tools-only --docker requires access to
the dockerfile. For now just report an error for --src-tarball, and
"docker build" will fail if not in a source tree. Another possibility
could be to host our container images on a public registry, and use
"FROM qemu:fedora" to make the Dockerfile small enough that it can be
included directly in the run-coverity-scan script.
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'dump')
0 files changed, 0 insertions, 0 deletions
