-
Notifications
You must be signed in to change notification settings - Fork 3.5k
ci: remove sonarqube #18273
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: remove sonarqube #18273
Conversation
this service will be decomissioned shortly
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like CI failures are due to not being able to get resources. Retried. Thanks for doing this! We are tracking this with #18215 this PR will close that issue!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💛 Build succeeded, but was flaky
Failed CI Steps
History
cc @v1v |
@Mergifyio backport 8.18 8.19 9.1 9.2 |
✅ Backports have been created
|
this service will be decommissioned shortly (cherry picked from commit cbef078) # Conflicts: # .buildkite/pull_request_pipeline.yml
this service will be decommissioned shortly (cherry picked from commit cbef078)
this service will be decommissioned shortly (cherry picked from commit cbef078) # Conflicts: # .buildkite/pull_request_pipeline.yml
this service will be decommissioned shortly (cherry picked from commit cbef078)
Release notes
[rn:skip]
What does this PR do?
Remove sonarqube analysis in the CI and in the build system
Why is it important/What is the impact to the user?
This service will be decommissioned shortly
Checklist
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs