Elastic CI Stack for AWS v2.1.4

What's changed?

• Buildkite Agents v3.0.0-beta28
• Edge agent version is downloaded when instances boot rather than baked in AMI
• Added SECRETS_PLUGIN_ENABLED to allow secrets downloading to be disabled

Upgrading

2. Perform a CloudFormation stack update with the following URL:
   https://s3.amazonaws.com/buildkite-aws-stack/v2.1.4/aws-stack.json

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):

Documentation

See the Readme for this release.

Elastic CI Stack for AWS v2.1.3

What's been fixed?

• Updated to latest Amazon Linux 2017.03.1 (see security advisory AWS-2017-007)
• Updated docker-compose to 1.14.0

Upgrading

1. Perform a CloudFormation stack update with the following URL:
   https://s3.amazonaws.com/buildkite-aws-stack/v2.1.3/aws-stack.json

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):

Documentation

See the Readme for this release.

Elastic CI Stack for AWS v2.1.2

What's been fixed?

• Using an env secrets bucket hook caused builds to fail with an undefined variable error

Upgrading

1. Perform a CloudFormation stack update with the following URL:
   https://s3.amazonaws.com/buildkite-aws-stack/v2.1.2/aws-stack.json

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):

Documentation

See the Readme for this release.

Elastic CI Stack for AWS v2.1.1

What's changed?

• 🐳 Docker-Compose 1.14.0-r2 (with support for cache_from directive)
• Buildkite Agents v2.6.3 and v3.0.0-beta27
• Agent version defaults to beta rather than stable

What's been fixed?

• Using git-credentials was broken (#290)
• Managed secrets bucket failed to create (#282)

Upgrading

2. Perform a CloudFormation stack update with the following URL:
   https://s3.amazonaws.com/buildkite-aws-stack/v2.1.1/aws-stack.json

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):

Documentation

See the Readme for this release.

Elastic CI Stack for AWS v2.1.0

What's new?

• A secrets bucket is created automatically if left blank
• Git over HTTPS is supported via a git-credentials file
• A customisable ScaleDownPeriod parameter is available to prevent rapid scale downs

What's changed?

• 🐳 Docker 17.05.0-ce and Docker-Compose 1.13.0
• Buildkite Agents v2.6.3 and v3.0.0-beta23
• Latest aws-cli
• Autoscaling group is replaced on update, for smoother updates in large groups

What's been fixed?

• Fixed a bug where the stack would scale up faster than instances were launching

Upgrading

2. Perform a CloudFormation stack update with the following URL:
   https://s3.amazonaws.com/buildkite-aws-stack/v2.1.0/aws-stack.json

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):

Documentation

See the Readme for this release.

Elastic CI Stack for AWS v2.0.2

This is a bug fix release for version 2.0.1 of the Elastic CI Stack for AWS.

What's been fixed?

• 🕷 Avoid restarting docker whilst it's initializing to try and avoid corrupting it (#236)

Upgrading

2. Perform a CloudFormation stack update with the following URL:
   https://s3.amazonaws.com/buildkite-aws-stack/v2.0.2/aws-stack.json

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):

Documentation

See the Readme for this release.

Elastic CI Stack for AWS v2.0.1

This is a bug fix release for version 2.0.0 of the Elastic CI Stack for AWS.

What's been fixed?

• ⏰ Increase the polling duration for scale down events to prevent hitting api limits (#263)
• 🆙 Includes new Buildkite Agent v2.5.1 (stable) and v3.0-beta.19 (beta)

Upgrading

2. Perform a CloudFormation stack update with the following URL:
   https://s3.amazonaws.com/buildkite-aws-stack/v2.0.1/aws-stack.json

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):

Documentation

See the Readme for this release.

Elastic CI Stack for AWS v2.0.0

What's new?

• Docker 17.03.0-ce and Docker-Compose 1.11.2
• Metrics are collected by a Lambda function, so no more metrics sub-stack 🎉
• Secrets bucket uses KMS-backed SSE by default
• Support authenticated S3 paths for BootstrapScriptUrl and AuthorizedUsersUrl
• New regions (US Ohio)
• ECRAccessPolicy parameter for easy Amazon ECR configuration
• Fixed size stacks are possible, and don't create auto-scaling resources
• Added version number to stack description and agent metadata
• Optionally non-public agent instances

What's been fixed?

• Improved scale-up/scale-down logic
• Cloudwatch logs are sent to correct region
• Fixed size stacks are support
• Correct release names for beta and edge agent
• Better error handling for when fetching env or private-key fails
• Regions that require v4 signatures are better handled
• Working docker-gc script
• Autoscaling is suspended during stack updates

Breaking changes

• ManagedPolicyARNs has been removed, a singular version exists now: ManagedPolicyARN
• Initialization logs have moved to /var/log/elastic-stack.log

Upgrading

1. If you're upgrading from v1.1, first ensure that any running agents have been terminated by removing the autoscaling rules and editing your ASG to a desired count of 0.
2. Perform a CloudFormation stack update with the following URL:
   https://s3.amazonaws.com/buildkite-aws-stack/v2.0.0/aws-stack.json
3. Update any parameters that are no longer supported and review new ones

If you want to launch a new stack, you can use this link:

Documentation

See the Readme for this release.

Elastic CI Stack for AWS v1.1.1

This is a bug fix release for version 1.1 of the Elastic CI Stack for AWS.

What's been fixed?

• 👭 If you run multiple agents per instance, chmod during build environment setup no longer clashes (#143)
• 🔐 The AWS_ECR_LOGIN_REGISTRY_IDS option has been fixed, so it now calls aws ecr get-login --registry-ids correctly (#141)

Upgrading

1. If you're upgrading from v1.0, first ensure that any running agents have been terminated by removing the autoscaling rules and editing your ASG to a desired count of 0. If you're upgrading from v1.1, then you can go straight to the next step.
2. Perform a CloudFormation stack update with the following URL:
   https://s3.amazonaws.com/buildkite-aws-stack/v1.1.1/aws-stack.json

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):

Documentation

See the Readme for this release.

Elastic CI Stack for AWS v1.1

Thanks to many contributions and lots of great feedback, we’re happy to announce version 1.1 of the Elastic CI Stack for AWS.

What's new?

• 📡 Buildkite Agent has been updated to the latest builds
• 🐳 Docker has been upgraded to 1.12.1
• 🐳 Docker Compose has been upgraded to 1.8.0
• 🔒 Can now add a custom managed policy ARN to apply to instances to add extra permissions to agents
• 📦 You can now specify a BootstrapScriptUrl to a bash script in an S3 bucket for performing your own setup and install tasks on agent machine boot
• 🔑 Added support for a single SSH key at the root of the secrets bucket (and SSH keys have been renamed)
• 🐳 Added support for logging into any Docker registry, and built-in support for logging into AWS ECR (N.B. the docker login environment variables have been renamed)
• 📄 Docker, cloud-init and CloudFormation logs are sent to CloudWatch logs
• 📛 Instances now have nicer names
• ⚡ Updating stack parameters now triggers instances to update, no need for deleting and recreating the stack

What's been fixed?

• 🚥 The "queue" parameter is now "default" by default, to make it easier and less confusing to get started. Make sure to update it to "elastic" if you want to continue using that queue name.
• 🐳 Jobs sometimes starting before Docker had started has been fixed
• ⏰ Rolling upgrades and stack updates are now more reliable, no longer should you get stack timeouts

Upgrading

1. If your stack is running less than 5 agents currently then skip to step 2. Otherwise, if your stack is running more than 5 agents, before running an update we recommend first terminating any running agents by removing the autoscaling rules and editing your ASG to a desired count of 0. This is due to the rolling update method being changed (it's now much more reliable), otherwise your agents might get stuck in a Terminating:wait state (which you can fix with complete-lifecycle-action).
2. Use CloudFormation stack update with the following URL:
   https://s3.amazonaws.com/buildkite-aws-stack/v1.1/aws-stack.json

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):

Documentation

See the Readme for this release.