Skip to content

Conversation

v1v
Copy link
Member

@v1v v1v commented Oct 6, 2025

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

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files (and/or docker env variables)
  • I have added tests that prove my fix is effective or that my feature works

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

this service will be decomissioned shortly
@v1v v1v requested review from a team October 6, 2025 14:00
@v1v v1v self-assigned this Oct 6, 2025
@v1v v1v added the backport-active-all Automated backport with mergify to all the active branches label Oct 6, 2025
Copy link
Contributor

github-actions bot commented Oct 6, 2025

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

Copy link
Member

@donoghuc donoghuc left a 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!

Copy link
Contributor

@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@elasticmachine
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

History

cc @v1v

@v1v v1v merged commit cbef078 into elastic:main Oct 7, 2025
13 checks passed
Copy link
Contributor

github-actions bot commented Oct 7, 2025

@Mergifyio backport 8.18 8.19 9.1 9.2

Copy link
Contributor

mergify bot commented Oct 7, 2025

backport 8.18 8.19 9.1 9.2

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Oct 7, 2025
this service will be decommissioned shortly

(cherry picked from commit cbef078)

# Conflicts:
#	.buildkite/pull_request_pipeline.yml
mergify bot pushed a commit that referenced this pull request Oct 7, 2025
this service will be decommissioned shortly

(cherry picked from commit cbef078)
mergify bot pushed a commit that referenced this pull request Oct 7, 2025
this service will be decommissioned shortly

(cherry picked from commit cbef078)

# Conflicts:
#	.buildkite/pull_request_pipeline.yml
mergify bot pushed a commit that referenced this pull request Oct 7, 2025
this service will be decommissioned shortly

(cherry picked from commit cbef078)
v1v pushed a commit that referenced this pull request Oct 7, 2025
v1v pushed a commit that referenced this pull request Oct 7, 2025
v1v pushed a commit that referenced this pull request Oct 7, 2025
v1v pushed a commit that referenced this pull request Oct 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-active-all Automated backport with mergify to all the active branches
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants