buildkite/elastic-ci-stack-for-aws v7.2.0 on GitHub

What's Changed

Changed

Update the bundled Linux and Windows Agents from v4.0.8 to v4.1.0. This includes Agent v4.0.9, which redacts Buildkite tokens by prefix in job logs, and fixes intermittent Windows crashes caused by process handles being closed twice #1900.

Fixed

Fix the Linux instance termination fallback that keeps desired capacity. It now passes --no-should-decrement-desired-capacity, so the AWS CLI no longer rejects the request and the Auto Scaling group replaces the instance #1899.

Agent Changelog (v4.0.9–v4.1.0)

v4.1.0

What's Changed

🐛 Fixed

Fix intermittent Windows crashes caused by process handles being closed twice by @moskyb in buildkite/agent#4432

🔧 Changed

Report cache save and restore timings and sizes to Buildkite when buildkite-agent cache save and buildkite-agent cache restore complete by @buildkate in buildkite/agent#4434
Add buildkite.commit, buildkite.pull_request and buildkite.build_author tracing attributes to job spans and OpenTelemetry resource attributes by @silesky in buildkite/agent#4435

🏠 Internal

Source release notes from release PR description by @moskyb in buildkite/agent#4429
Check backports against the v3 backport policy by @moskyb in buildkite/agent#4433

New Contributors

@silesky made their first contribution in buildkite/agent#4435

Full Changelog: buildkite/agent@v4.0.9...v4.1.0

v4.0.9

What's Changed

🔒 Security

A-1975: Redact Buildkite tokens by prefix in job logs by @zhming0 in buildkite/agent#4425

🐛 Fixed

A-1915: Close the job log tmpfile once the job is done, not when the process exits by @zhming0 in buildkite/agent#4422

🏠 Internal

Make the release skill use semver more effectively by @moskyb in buildkite/agent#4428

Full Changelog: buildkite/agent@v4.0.8...v4.0.9

Full Changelog: v7.1.0...v7.2.0

Upgrading

Follow the v7 upgrade guide before updating. Remove or replace retired parameters in parameter files and deployment automation. If you use a custom AMI through ImageId or ImageIdParameter, rebuild it from the v7 base AMI and update it in the same stack update; a v6-based AMI might not boot under the v7 template depending on the configuration.

Perform a CloudFormation stack update with the following URL:

https://s3.amazonaws.com/buildkite-aws-stack/v7.2.0/aws-stack.yml

If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):