Skip to content

azure: fix Coverity pipeline #5382

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Feb 7, 2020
Merged

azure: fix Coverity pipeline #5382

merged 3 commits into from
Feb 7, 2020

Conversation

pks-t
Copy link
Member

@pks-t pks-t commented Feb 4, 2020

The Coverity pipeline has been broken since July 2019. Nobody except @tiennou complained, and I didn't care to look until now. This PR finally fixes the issues and brings Coverity back to live as seen in the latest Coverity test build. I first wanted to just convert to curl, which was the most important issue. But the script failed in some more places, which is why I then decided to refactor our Coverity script completely and make it much simpler.

@pks-t pks-t force-pushed the pks/azure-coverity branch from 30965de to f8df1d3 Compare February 4, 2020 13:27
@pks-t
Copy link
Member Author

pks-t commented Feb 4, 2020

Wasn't sure if the build succeeded, but Coverity now says analysis is queued. Meaning: this PR is ready to be merged

pks-t added 3 commits February 7, 2020 10:41
In commit bbc0b20 (azure: fix Coverity's build due to wrong container
name, 2019-08-02), Coverity builds were fixed to use the correct
container names. Unfortunately, the "fix" completely broke our Coverity
builds due to using wrong syntax for the Docker task. Let's fix this by
using "imageName" instead of the Docker dict.
Back in commit 5a6740e (azure: build Docker images as part of the
pipeline, 2019-08-02), we have converted our pipelines to use self-built
Docker images to ease making changes to our Dockerfiles. The commit
didn't adjust our Coverity pipeline, though, so let's do this now.
There's several issues with our Coverity builds, like e.g. missing wget
in our containers. Simplify our Coverity pipeline and fix these issues.
@pks-t pks-t force-pushed the pks/azure-coverity branch from f8df1d3 to 86c54cc Compare February 7, 2020 09:45
@pks-t
Copy link
Member Author

pks-t commented Feb 7, 2020

Started another run and Coverity now spits out defects again. There's no risk of breaking anything except Coverity, so I'm merging this

@pks-t pks-t merged commit 65ac33a into master Feb 7, 2020
@pks-t pks-t deleted the pks/azure-coverity branch February 7, 2020 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant