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.

Sign up for GitHub

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

Jump to bottom

Sonarqube runs with failed tests shouldn't be failed workflow runs #6987

Open
jflo opened this issue Apr 23, 2024 · 0 comments
Open

Sonarqube runs with failed tests shouldn't be failed workflow runs #6987

jflo opened this issue Apr 23, 2024 · 0 comments
Labels
P4 Low (ex: Node doesn't start up when the configuration file has unexpected "end-of-line" character)

Comments

@jflo
Copy link
Contributor

jflo commented Apr 23, 2024

If you look at the history of Sonarqube actions, they don't always pass, despite having done their analysis and published it correctly. I suspect this is due to flaky tests, flaking during the course of the build target.

Can we setup this action to only fail if there was a problem with sonar analysis or publishing?
@jflo jflo added the P4 Low (ex: Node doesn't start up when the configuration file has unexpected "end-of-line" character) label Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P4 Low (ex: Node doesn't start up when the configuration file has unexpected "end-of-line" character)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jflo