Lachlan Donald
Lachlan Donald
4Mb is pretty much 3 days internet usage for @andrewk.
Currently the agent doesn't respect `AWS_PROFILE` or the shared credentials files in `~/.aws`. This is because this wasn't initially supported in the AWS SDK. I think this would probably be...
Historically this wasn't added due to --tags not being supported in earlier git versions (#338), but that was 2016. By now it's well supported and optimized so it's quite fast....
Currently the agent will download a plugin for something like `blah-blah-plugin` from the master branch the first time it needs it, but it won't update it ever again. This means...
Currently the agent supports looking up meta-data by job, but this can be awkward in triggered builds where you are trying to lookup meta-data on the original build. buildkite-agent meta-data...
The agent should support retry with backoff for artifact downloads to avoid network or rate limiting issues.
Up until this point, we've recommended that folks concerned with security in the agent disable plugins because they could allow a variety of attacks, specifically: * Users could reference plugins...
Based on a conversation with @keithpitt and I, we realized that supporting metadata scoped wider than the current build scope would be pretty straightforward. The thinking was to add "scope"...
We use ECS for auto-scaling build agents for buildkite.com. We are using [custom metrics and several Lambdas](https://github.com/buildkite/elastic-ci-stack-for-aws-ecs) for scaling the ECS service that runs our agent based on pending CI...