Skip to content

Releases: buildkite/elastic-ci-stack-for-aws

v6.51.0

12 Dec 13:19
d2af53e

Choose a tag to compare

v6.51.0 (2025-12-12)

Changed

Added

Internal

  • fix: ensure AMI metadata is set for copy step when builds are skipped #1689 (scadu)
  • Fix versions.ps1 matching in Renovate config #1688 (scadu)
  • Fix Renovate for tooling using versions.{sh,ps1} scripts #1686 (scadu)
  • Do not rebuild Stack AMI when not needed #1681 (scadu)

Agent Changelog

v3.115.1 (2025-12-12)

Full Changelog

Fixes

  • PS-1491: Fix double retry issue for k8s mode bootstrap #3628 (@zhming0)

Internal

  • PB-1023: remove old kubernetes bootstrap setup #3629 (@zhming0)
  • chore(deps): update zstash to v0.6.0 and update progress callback #3630 (@wolfeidau)
  • feat: add support for concurrent save and restore operations #3627 (@wolfeidau)

v3.115.0 (2025-12-10)

Full Changelog

Added

  • --changed-files-path for pipeline upload, which allows users to specify a list of files changed for if_changed computation #3620 (@pyrocat101)

Fixes

  • Further fixes to custom bucket artifact uploads/downloads #3615 (@moskyb)

Internal

v3.114.1 (2025-12-05)

Full Changelog

Fixed

  • Fix issue where artifacts uploaded to customer-managed s3 buckets could not be downloaded #3607 (@moskyb)

Internal

v6.50.0

26 Nov 21:31
1c45ea5

Choose a tag to compare

v6.50.0 (2025-11-26)

Changed

Internal

  • Update changelog for the v6.49.0 release by @scadu in #1678

Upgrading

Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.50.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):

Launch Buildkite AWS Stack

v6.49.0

25 Nov 12:36
06fd666

Choose a tag to compare

v6.49.0 (2025-11-25)

Changed

Added

Internal

  • chore: add a pr template #1674 (mcncl)
  • Update changelog for upcoming release v6.48.0 #1670 (scadu)

Agent Changelog

v3.114.0 (2025-11-25)

Full Changelog

Added

Fixed

  • Fix for the agent sometimes failing to disconnect properly when exiting - agent pool: Send error after disconnecting #3596 (@DrJosh9000)

Internal

Dependency updates

  • build(deps): bump the cloud-providers group with 7 updates #3593 (@dependabot[bot])
  • build(deps): bump the container-images group across 5 directories with 1 update #3594 (@dependabot[bot])
  • build(deps): bump the container-images group across 1 directory with 2 updates #3595 (@dependabot[bot])
  • build(deps): bump golang.org/x/crypto from 0.44.0 to 0.45.0 #3590 (@dependabot[bot])

Upgrading

Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.49.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):

Launch Buildkite AWS Stack

v6.48.0

19 Nov 12:44
5ae8829

Choose a tag to compare

v6.48.0 (2025-11-19)

Changed

Added

Internal

  • Actually make base images private #1658 (scadu)
  • Make base AMI private #1657 (scadu)
  • Revert "Don't rebuild Stack AMI when not needed" #1669 (scadu)
  • Fix: skip publish when only templates change #1664 (scadu)
  • Fix Stack AMI builds #1663 (scadu)
  • Don't rebuild Stack AMI when not needed #1661 (scadu)
  • Update changelog for upcoming release v6.47.0 #1655 (scadu)
Agent Changelog

v3.113.0

Compare Source

Full Changelog

Added
Fixed
Internal
Dependency updates

v3.112.0

Compare Source

Full Changelog

Added
Fixed
Internal
Dependency updates

Upgrading

Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.48.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):

Launch Buildkite AWS Stack

v6.47.0

12 Nov 15:52
a9a0cf1

Choose a tag to compare

v6.47.0 (2025-11-12)

Fixed

Added

Internal

Dependencies

Full Changelog: v6.45.0...v6.46.0

Upgrading

Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.47.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):

Launch Buildkite AWS Stack

v6.46.0

04 Nov 13:28
ff9eb58

Choose a tag to compare

v6.46.0 (2025-11-04)

Changed

  • chore(deps): update buildkite-agent to v3.110.0 by @renovate[bot] in #1632

Internal

  • chore: remove unused workflow file by @mcncl in #1628
  • chore(deps): update buildkite plugin docker-compose to v5.11.0 by @renovate[bot] in #1626
  • Fix Renovate custom manager for buildkite-agent by @scadu in #1631
  • chore: remove notes from Renovate's PR by @scadu in #1633
Agent Changelog

v3.110.0

Compare Source

Full Changelog

Added
Changed

Various improvements and fixes to do with signal and cancel grace periods, and signal handling, most notably:

  • When cancelling a job, the timeout before sending a SIGKILL to the job has changed from cancel-grace-period to signal-grace-period (--signal-grace-period-seconds flag, BUILDKITE_SIGNAL_GRACE_PERIOD_SECONDS env var) to allow the agent some extra time to upload job logs and mark the job as finished. By default, signal-grace-period is 1 second shorter than cancel-grace-period. You may wish to increase cancel-grace-period accordingly.
  • When SIGQUIT is handled by the bootstrap, the exit code is now 131, and it no longer dumps a stacktrace.
  • The recently-added --kubernetes-log-collection-grace-period flag is now deprecated. Instead, use --cancel-grace-period.
  • When running the agent interactively, you can now Ctrl-C a third time to exit immediately.
  • In Kubernetes mode, the agent now begins shutting down on the first SIGTERM. The kubernetes-bootstrap now swallows SIGTERM with a logged message, and waits for the agent container to send an interrupt.
  • When the agent is cancelling jobs because it is stopping, all jobs start cancellation simultaneously. This allows the agent to exit sooner when multiple workers (--spawn flag) are used.
    See #​3549, #​3547, #​3534 (@​DrJosh9000)
Fixed
Internal
Dependency updates

v3.109.1

Compare Source

Full Changelog

Added
Changed

Various improvements and fixes to do with signal and cancel grace periods, and signal handling, most notably:

  • When cancelling a job, the timeout before sending a SIGKILL to the job has changed from cancel-grace-period to signal-grace-period (--signal-grace-period-seconds flag, BUILDKITE_SIGNAL_GRACE_PERIOD_SECONDS env var) to allow the agent some extra time to upload job logs and mark the job as finished. By default, signal-grace-period is 1 second shorter than cancel-grace-period. You may wish to increase cancel-grace-period accordingly.
  • When SIGQUIT is handled by the bootstrap, the exit code is now 131, and it no longer dumps a stacktrace.
  • The recently-added --kubernetes-log-collection-grace-period flag is now deprecated. Instead, use --cancel-grace-period.
  • When running the agent interactively, you can now Ctrl-C a third time to exit immediately.
  • In Kubernetes mode, the agent now begins shutting down on the first SIGTERM. The kubernetes-bootstrap now swallows SIGTERM with a logged message, and waits for the agent container to send an interrupt.
  • When the agent is cancelling jobs because it is stopping, all jobs start cancellation simultaneously. This allows the agent to exit sooner when multiple workers (--spawn flag) are used.
    See #​3549, #​3547, #​3534 (@​DrJosh9000)
Fixed
Internal
Dependency updates
  • Upgrade Datadog-go to v5.8.1 to work around mod checksum issues #​3538 (@​dannyfallon)
  • build(deps): bump the container-images group across 3 directories with 2 updates #​3545 (@​dependabot[bot])
  • build(deps): bump g...
Read more

v6.45.0

31 Oct 17:30
51b4205

Choose a tag to compare

What's Changed

Full Changelog: v6.44.0...v6.45.0

v6.44.0

31 Oct 12:13
8cc46d8

Choose a tag to compare

What's Changed

Full Changelog: v6.43.0...v6.44.0

v6.43.0

09 Oct 14:23
v6.43.0
9399dc8

Choose a tag to compare

Note

We've identified an issue with how our docker-compose plugin interacts with the ecr-login Docker credential helper in our ecr plugin.
This release disables AWS ECR Credential Helper as the default login method for the ecr plugin while we investigate.

v6.43.0 (2025-10-09)

Changed

  • Add signing parameters to cfn template by @moskyb in #1263

Fixed

Documentation

Full Changelog

v6.42.0

07 Oct 14:19
v6.42.0
ce349c2

Choose a tag to compare

v6.42.0 (2025-10-07)

Changed

Internal

  • Update golang Docker tag to v1.25 by @renovate[bot] in #1610
  • Updates to clarify BootstrapScriptUrl and AgentEnvFileUrl Stack params by @petetomasik in #1611
  • Update changelog for v6.41.6 release #1602 (scadu)

Full Changelog: v6.41.6...v6.42.0