On Tue, 14 Apr 2020 at 12:58, Philippe Mathieu-Daudé wrote:
> On 3/19/20 8:33 PM, Peter Maydell wrote:
> > +# TODO: This re-downloads the tools every time, rather than
> > +# caching and reusing the image produced with the downloaded tools.
> > +# Not sure why.
>
> I remember something
On 4/14/20 1:58 PM, Philippe Mathieu-Daudé wrote:
On 3/19/20 8:33 PM, Peter Maydell wrote:
Add support for running the Coverity Scan tools inside a Docker
container rather than directly on the host system.
Signed-off-by: Peter Maydell
---
v1->v2:
* various bug fixes
* added --src-tarball r
On 3/19/20 8:33 PM, Peter Maydell wrote:
Add support for running the Coverity Scan tools inside a Docker
container rather than directly on the host system.
Signed-off-by: Peter Maydell
---
v1->v2:
* various bug fixes
* added --src-tarball rather than putting the whole source
tree in the
On 19/03/20 20:33, Peter Maydell wrote:
> +# TODO: how do you get 'docker build' to print the output of the
> +# commands it is running to its stdout? This would be useful for debug.
> +DOCKER_BUILDKIT=1 docker build -t coverity-scanner \
> + --secret id=coverity.token
Add support for running the Coverity Scan tools inside a Docker
container rather than directly on the host system.
Signed-off-by: Peter Maydell
---
v1->v2:
* various bug fixes
* added --src-tarball rather than putting the whole source
tree in the 'secrets' directory
* docker file package li