[8.17][Automation] Bump VM Image version to 1752886846

[github-actions]

Bump vm-images to latest version

Update .buildkite/pipeline.yml

1 file(s) updated with "$1: \"platform-ingest-elastic-agent-$2-1752886846\"": * .buildkite/pipeline.yml

Update .buildkite/bk.integration.pipeline.yml

1 file(s) updated with "$1: \"platform-ingest-elastic-agent-$2-1752886846\"": * .buildkite/bk.integration.pipeline.yml

GitHub Action workflow link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 7a14d26

Failed CI Steps

• Windows:2022:amd64:sudo
• Windows:2022:amd64:sudo
• Windows:2025:amd64:sudo
• Windows:2025:amd64:sudo
• Ubuntu:2404:amd64:sudo
• Ubuntu:2404:amd64:sudo

History

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[pkoutsovasilis]

@v1v this failed because the serverless project got deleted, did you manage to have a look at this issue? 🙂

[v1v]

@v1v this failed because the serverless project got deleted, did you manage to have a look at this issue? 🙂

Indeed, I'm working on having an understanding, and in fact I've already discussed with one of my team members. For this I was about to raise an internal ticket so we can debug a bit further

[mergify]

Automatically approving mergify

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ❌ buildkite/elastic-agent

You can check the last failing draft PR here: #9083.

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.