Skip to content
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

CI: specify coverity version in coverity.yml #3556

Merged
merged 1 commit into from
Apr 5, 2024

Conversation

jadenabrams100
Copy link
Contributor

The Coverity Scan GitHub action is failing due to not being able to find the supported Coverity version. This fix attempts to fix the error by adding in the version of Coverity specified in the Coverity defects dashboard.

@github-actions github-actions bot added the CI Continuous integration label Apr 3, 2024
@echoix
Copy link
Member

echoix commented Apr 4, 2024

Is there any way to know before merging if it fixes the problem? If no, I'll just let it merge.

@echoix
Copy link
Member

echoix commented Apr 4, 2024

@jadenabrams100
Copy link
Contributor Author

@echoix I am not able to determine if this would fix the issue, but I hope it does fix it!

@echoix
Copy link
Member

echoix commented Apr 5, 2024

So let's try it, come back with another PR if it's not enough. It won't affect much if it doesn't help.

@echoix echoix merged commit 0cd72be into OSGeo:main Apr 5, 2024
27 checks passed
@nilason
Copy link
Contributor

nilason commented Apr 5, 2024

Well, this didn't do it.
See https://github.com/OSGeo/PROJ/actions/workflows/coverity-scan.yml for a working, alternative approach.

@jadenabrams100
Copy link
Contributor Author

Well, this didn't do it. See https://github.com/OSGeo/PROJ/actions/workflows/coverity-scan.yml for a working, alternative approach.

I will try that out and see it it works, thank you!

@neteler neteler added this to the 8.4.0 milestone Apr 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants