ci: add an individual coverity pipeline #4964
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
10b948d to
7bd3406
Compare
Coverity is back but it's only read-only! Agh. Just allow it to fail and not impact the overall job run.
7bd3406 to
52a97ee
Compare
|
@tiennou, you had the right idea all along. I've gone ahead and set up a new nightly build in Azure Pipelines for this particular build definition. |
|
Isolation FTW 😉. Let's hope write-access is restored soon, as I'm still waiting to see the effects of modeling from #4922. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Split the Coverity runs into its own pipeline. Give this new pipeline two steps: the build step, which may not fail (otherwise the overall pipeline will fail), and the publish step (which may fail, which would cause the pipeline to "partially succeed").