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

Fail the CI if certain warnings are found #2164

Open
Xazax-hun opened this issue Jun 5, 2019 · 2 comments
Open

Fail the CI if certain warnings are found #2164

Xazax-hun opened this issue Jun 5, 2019 · 2 comments
Labels
analyzer 📈 Related to the analyze commands (analysis driver) CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands discussion 💡 enhancement 🌟 usability 👍 Usability-related features

Comments

@Xazax-hun
Copy link
Contributor

Is your feature request related to a problem? Please describe.
This feature request was mentioned on cfe-dev mailing list and the use-case is already supported by scan-build: http://lists.llvm.org/pipermail/cfe-dev/2019-June/062495.html

Describe the solution you'd like
It should be possible to treat certain checkers or compiler warnings as compilation errors.

Describe alternatives you've considered
Alternatively one could use parse to get the list of warnings from the run and process the result with a script. This is, however, not user friendly at all. We should not require the users to maintain additional scripts for such a simple task.

@Xazax-hun Xazax-hun added enhancement 🌟 CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands discussion 💡 analyzer 📈 Related to the analyze commands (analysis driver) usability 👍 Usability-related features labels Jun 5, 2019
@LebedevRI
Copy link
Contributor

the use-case is already supported by scan-build

I'm also missing scan-build's

 --status-bugs

   By default, the exit status of scan-build is the same as the executed build
   command. Specifying this option causes the exit status of scan-build to be 1
   if it found potential bugs and the exit status of the build itself otherwise.

Presumably it would be a flag to analyze sub-command.

@LebedevRI LebedevRI mentioned this issue Sep 23, 2020
@LebedevRI
Copy link
Contributor

@bruntib Looks like this can be closed now?
Hurray!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyzer 📈 Related to the analyze commands (analysis driver) CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands discussion 💡 enhancement 🌟 usability 👍 Usability-related features
Projects
None yet
Development

No branches or pull requests

2 participants