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

[8.10](backport #3108) Sonarqube buildkite integration #3446

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Sep 20, 2023

This is an automatic backport of pull request #3108 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

* Sonarqube buildkite integration

* Sonarqube buildkite integration

* Fixed git log

* Run unit tests on a VM

* Execute ut on main branch

* Removed sonarcloud github workflow

* Added retry to go download

* removed CodeCoverage (build.yml) GHA workflow

* Run buildkite unit tests on each pull request

* Run buildkite unit tests on each pull request

* Run buildkite unit tests on each pull request

* Run buildkite unit tests on each pull request

* Run buildkite unit tests on each pull request

* Added a test file for sonar analysis

* Added a test file for sonar analysis

* cleanup

* Merged with main

* Added echo to unit tests

* Added echo to unit tests

* Fix common.sh logging

* Try old way on go installation

* Removed comments

* check: added not covered file to test sonar notifications

* removed the test file

(cherry picked from commit 2e9a256)
@mergify mergify bot requested a review from a team as a code owner September 20, 2023 17:00
@mergify mergify bot requested review from AndersonQ and pchila and removed request for a team September 20, 2023 17:00
@mergify mergify bot added the backport label Sep 20, 2023
@mergify mergify bot assigned pazone Sep 20, 2023
@mergify
Copy link
Contributor Author

mergify bot commented Sep 20, 2023

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.10/pr-3108 upstream/mergify/bp/8.10/pr-3108
git merge upstream/8.10
git push upstream mergify/bp/8.10/pr-3108

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-09-20T17:00:33.976+0000

  • Duration: 27 min 11 sec

Test stats 🧪

Test Results
Failed 0
Passed 6251
Skipped 57
Total 6308

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages.

  • run integration tests : Run the Elastic Agent Integration tests.

  • run end-to-end tests : Generate the packages and run the E2E Tests.

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

@elasticmachine
Copy link
Contributor

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 98.765% (80/81) 👍
Files 67.719% (193/285) 👍
Classes 66.292% (354/534) 👍
Methods 53.079% (1112/2095) 👍
Lines 38.635% (12678/32815) 👎 -0.003
Conditionals 100.0% (0/0) 💚

@mergify
Copy link
Contributor Author

mergify bot commented Sep 25, 2023

This pull request has not been merged yet. Could you please review and merge it @pazone? 🙏

1 similar comment
@mergify
Copy link
Contributor Author

mergify bot commented Oct 2, 2023

This pull request has not been merged yet. Could you please review and merge it @pazone? 🙏

@pierrehilbert pierrehilbert added the Team:Elastic-Agent Label for the Agent team label Oct 8, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

@pierrehilbert pierrehilbert requested a review from pazone October 8, 2023 12:19
@mergify
Copy link
Contributor Author

mergify bot commented Oct 9, 2023

This pull request has not been merged yet. Could you please review and merge it @pazone? 🙏

1 similar comment
@mergify
Copy link
Contributor Author

mergify bot commented Oct 16, 2023

This pull request has not been merged yet. Could you please review and merge it @pazone? 🙏

@pierrehilbert
Copy link
Contributor

@pazone what should we do with this one?

@mergify
Copy link
Contributor Author

mergify bot commented Oct 23, 2023

This pull request has not been merged yet. Could you please review and merge it @pazone? 🙏

@mergify
Copy link
Contributor Author

mergify bot commented Oct 30, 2023

This pull request has not been merged yet. Could you please review and merge it @pazone? 🙏

@cmacknz
Copy link
Member

cmacknz commented Oct 30, 2023

Let's just close this, no more planned 8.10 releases.

@cmacknz cmacknz closed this Oct 30, 2023
@cmacknz cmacknz deleted the mergify/bp/8.10/pr-3108 branch October 30, 2023 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Team:Elastic-Agent Label for the Agent team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants