Skip to content

Buildkite Pipeline - AWS infra related improvements #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
thundergolfer opened this issue May 19, 2019 · 1 comment
Open

Buildkite Pipeline - AWS infra related improvements #1

thundergolfer opened this issue May 19, 2019 · 1 comment
Labels
DevOps C.I, C.D enhancement New feature or request

Comments

@thundergolfer
Copy link
Owner

My Buildkite setup is now at a stage where I can run bazel test //... and have things pass 😄, but things are far from perfect.

Improvements to be made:

  1. Currently cannot access like buildkite-agent instances. The Buildkite CloudFormation template has something about ssh keyPair that can supposedly address this
  2. EC2 Instance setup currently happens in the bootstrap_agent.sh script. I think it would be much better to bake this setup into an AMI and then use that as the agent AMI instead of the base buildkite-stack AMIs. Having 1 from this list will help achieve this.
  3. Lower Priority: I had to go up from t2-nano to t2-small to avoid a JVM out-of-memory error. See if I can do some tuning or find a better instance type for these BK agents.
@thundergolfer thundergolfer added enhancement New feature or request DevOps C.I, C.D labels May 19, 2019
@thundergolfer
Copy link
Owner Author

  1. My buildkite-agent instances are terminating after every completed step!!! Need them to stay up for at least 5 minutes or so waiting to see if it can pick up another step. Jeezus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DevOps C.I, C.D enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant