elastic-ci-stack-for-aws
elastic-ci-stack-for-aws copied to clipboard
buildkite
An auto-scaling cluster of build agents running in your own AWS VPC
**Describe the bug** As per the bug reported at https://github.com/git-lfs/git-lfs/issues/3524, it appears that git stores the entire thing in memory before writing it out to disk. If a git-lfs object...
**Is your feature request related to a problem? Please describe.** At the moment (2022-03-21) AMIs are released not very frequently. This means they are behind with security patches (see https://alas.aws.amazon.com/alas2.html),...
**Describe the bug** https://github.com/buildkite/elastic-ci-stack-for-aws/blame/master/utils/log-collector#L75 it seems `-v-1d` is a BSD/OSX syntax and not supported by the GNU `data`, https://man7.org/linux/man-pages/man1/date.1.html **Steps To Reproduce** Steps to reproduce the behavior: 1. ./log-collector -s...
**Is your feature request related to a problem? Please describe.** gp3 EBS volumes have a throughput parameter that can be configured. Currently this is not exposed in the elastic stack...
**Is your feature request related to a problem? Please describe.** This is no longer a problem for me because I've since modified my pipeline to run the AWS CLI inside...
**Is your feature request related to a problem? Please describe.** I have several buildkite nodes representing several different queues but all of them are named "buildkite-agent" on the AWS EC2...
It has been [reported](https://buildkite-community.slack.com/archives/C19BG77H9/p1633286321070200?thread_ts=1627868355.002700&cid=C19BG77H9) in Slack that this API call can be an intermittent source of job failure. This API call was added in v5.5.0 as part of [supporting cross-region...
Currently docker-compose is pinned to [v1.29.2](https://docs.docker.com/compose/release-notes/#1292) (2021-04-13) which is now over 12 months old and is a major release behind. https://github.com/buildkite/elastic-ci-stack-for-aws/blob/master/packer/linux/scripts/install-docker.sh#L6 Docker desktop etc have had considerable updates meaning most...
We want the agent process to remain alive but the bootstrap and any processes under it in the systemd service should be candidates for being killed under memory pressure 🤔
When log_stream_name is omitted from cloudwatch agent config, it defaults to the id of the instance sending the logs. This PR makes this choice explicit, bringing the windows config in...
