Skip to content

[9.0] (backport #8211) ci: reproducible builds using pinned VM images #8357

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
Merged
merged 1 commit into from
Jun 5, 2025
Merged

[9.0] (backport #8211) ci: reproducible builds using pinned VM images #8357

merged 1 commit into from
Jun 5, 2025

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Jun 5, 2025

What does this PR do?

Pin the VM images and automate the autobump.

The autobump will run weekly on Sundays and will raise a PR with the required changes.

Why is it important?

This will help with a stable CI.

Follow-ups

  • Simplify the backport strategy and use specific PRs creation per supported branch
  • Enable auto-merge

Checklist

  • I have read and understood the pull request guidelines of this project.
  • 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
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

$ GITHUB_TOKEN=$(gh auth token) \
  GITHUB_ACTOR=v1v \
  updatecli diff --config .ci/updatecli/updatecli-bump-vm-images.yml --values .ci/updatecli/values.d/scm.yml

produced

--- .buildkite/pipeline.yml
+++ .buildkite/pipeline.yml
@@ -6,12 +6,12 @@
 
   # The following images are defined here and their values will be updated by updatecli
   # Please do not change them manually.
-  IMAGE_UBUNTU_2204_X86_64: "platform-ingest-elastic-agent-ubuntu-2204-1744855248"
-  IMAGE_UBUNTU_2204_ARM_64: "platform-ingest-elastic-agent-ubuntu-2204-aarch64-1744855248"
-  IMAGE_WIN_2016: "platform-ingest-elastic-agent-windows-2016-1744855248"
-  IMAGE_WIN_2022: "platform-ingest-elastic-agent-windows-2022-1744855248"
-  IMAGE_WIN_10: "platform-ingest-elastic-agent-windows-10-1744855248"
-  IMAGE_WIN_11: "platform-ingest-elastic-agent-windows-11-1744855248"
+  IMAGE_UBUNTU_2204_X86_64: "platform-ingest-elastic-agent-ubuntu-2204-1754885210"
+  IMAGE_UBUNTU_2204_ARM_64: "platform-ingest-elastic-agent-ubuntu-2204-aarch64-1754885210"
+  IMAGE_WIN_2016: "platform-ingest-elastic-agent-windows-2016-1754885210"
+  IMAGE_WIN_2022: "platform-ingest-elastic-agent-windows-2022-1754885210"
+  IMAGE_WIN_10: "platform-ingest-elastic-agent-windows-10-1754885210"
+  IMAGE_WIN_11: "platform-ingest-elastic-agent-windows-11-1754885210"
 
 steps:
   - label: "check-ci"

⚠ - 1 file(s) updated with "$1: \"platform-ingest-elastic-agent-$2-1754885210\"":
	* .buildkite/pipeline.yml
DEBUG: Checking if local changes have been done that should be published
DEBUG: no changes detected between branches "test/updatecli-pin-vm-images" and "updatecli_test_updatecli-pin-vm-images_346f1fe4c0832026a247e5c8dfbbeb3bb5c71332f97a57986cfe4c6771f5182a"

target: target#update-buildkite-bk.integration.pipeline
-----------------------------------------------

**Dry Run enabled**

DEBUG: checkout git branch "updatecli_test_updatecli-pin-vm-images_346f1fe4c0832026a247e5c8dfbbeb3bb5c71332f97a57986cfe4c6771f5182a", based on "test/updatecli-pin-vm-images"
DEBUG: Relative path detected: changing from ".buildkite/bk.integration.pipeline.yml" to absolute path from SCM: "/var/folders/t7/ghqdh8cx2g12pwb_w0ncmw900000gn/T/updatecli/github/v1v/elastic-agent/.buildkite/bk.integration.pipeline.yml"
DEBUG: Match found for pattern "(IMAGE_.+): \"platform-ingest-elastic-agent-(.+)-(.+)\"" in file ".buildkite/bk.integration.pipeline.yml"
".buildkite/bk.integration.pipeline.yml" updated with [dry run] content "$1: \"platform-ingest-elastic-agent-$2-1754885210\""

--- .buildkite/bk.integration.pipeline.yml
+++ .buildkite/bk.integration.pipeline.yml
@@ -7,12 +7,12 @@
 
   # The following images are defined here and their values will be updated by updatecli
   # Please do not change them manually.
-  IMAGE_UBUNTU_2404_X86_64: "platform-ingest-elastic-agent-ubuntu-2404-1744855248"
-  IMAGE_UBUNTU_2404_ARM_64: "platform-ingest-elastic-agent-ubuntu-2404-aarch64-1744855248"
-  IMAGE_RHEL_8: "platform-ingest-elastic-agent-rhel-8-1744855248"
-  IMAGE_DEBIAN_12: "platform-ingest-elastic-agent-debian-12-1744855248"
-  IMAGE_WIN_2022: "platform-ingest-elastic-agent-windows-2022-1744855248"
-  IMAGE_WIN_2025: "platform-ingest-elastic-agent-windows-2025-1744855248"
+  IMAGE_UBUNTU_2404_X86_64: "platform-ingest-elastic-agent-ubuntu-2404-1754885210"
+  IMAGE_UBUNTU_2404_ARM_64: "platform-ingest-elastic-agent-ubuntu-2404-aarch64-1754885210"
+  IMAGE_RHEL_8: "platform-ingest-elastic-agent-rhel-8-1754885210"
+  IMAGE_DEBIAN_12: "platform-ingest-elastic-agent-debian-12-1754885210"
+  IMAGE_WIN_2022: "platform-ingest-elastic-agent-windows-2022-1754885210"
+  IMAGE_WIN_2025: "platform-ingest-elastic-agent-windows-2025-1754885210"

While with apply

$ GITHUB_TOKEN=$(gh auth token) \
  GITHUB_ACTOR=v1v \
  updatecli apply --config .ci/updatecli/updatecli-bump-vm-images.yml --values .ci/updatecli/values.d/scm.yml

Pull Request available at:

	https://github.com/v1v/elastic-agent/pull/6

DEBUG: Merging existing pull-request body with new report
Existing GitHub pull request found: https://github.com/v1v/elastic-agent/pull/6

=============================

SUMMARY:



⚠ Bump vm-images to latest version:
	Source:
		✔ [latestVersion] Get latest available build
	Condition:
		✔ [latestVersion-check] Check if defined latest version differs
	Target:
		⚠ [update-buildkite-bk.integration.pipeline] Update .buildkite/bk.integration.pipeline.yml
		⚠ [update-buildkite-pipeline] Update .buildkite/pipeline.yml


Run Summary
===========
Pipeline(s) run:
  * Changed:	1
  * Failed:	0
  * Skipped:	0
  * Succeeded:	0
  * Total:	1

One action to follow up:

v1v#6

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...
This is an automatic backport of pull request #8211 done by [Mergify](https://mergify.com).

@mergify mergify bot added the backport label Jun 5, 2025
@mergify mergify bot requested a review from a team as a code owner June 5, 2025 16:55
@mergify mergify bot added the backport label Jun 5, 2025
@mergify mergify bot assigned v1v Jun 5, 2025
@mergify mergify bot mentioned this pull request Jun 5, 2025
Merged
8 tasks
@v1v v1v enabled auto-merge (squash) June 5, 2025 17:03
@elastic-sonarqube
Copy link

elastic-sonarqube bot commented Jun 5, 2025

Quality Gate passed 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

@v1v v1v merged commit ae7615c into 9.0 Jun 5, 2025
14 checks passed
@v1v v1v deleted the mergify/bp/9.0/pr-8211 branch June 5, 2025 18:25
@elasticmachine
Copy link
Collaborator

elasticmachine commented Jun 5, 2025

💚 Build Succeeded

cc @v1v

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@v1v v1v v1v approved these changes

Assignees

@v1v v1v

Labels

backport skip-changelog

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@elasticmachine @v1v