Buildkite CLI
=============

A cli tool for interacting with buildkite.com from your terminal.

buildkite configure
-------------------

Sets up the tool, asks for a Buildkite graphql token and a default organization.

buildkite pipelines
-------------------

* `buildkite pipelines list`
* `buildkite pipelines create`
* `buildkite pipelines delete`

Create is the interesting one, it will look at a checked out repo and create a pipeline with that name with a single uploader step. It will use the git remote to set the checkout url for the pipeline. If it's a github repo, it will ask for a github oauth token to access that repo and it will setup webhooks. Finally, if no `.buildkite/pipeline.yml` exists locally, it will create an empty one.

At this point you are good to go.

buildkite builds
----------------

* `buildkite builds list`
* `buildkite builds create`
* `buildkite builds cancel`
* `buildkite builds rerun`

buildkite agents
----------------

* `buildkite agents list`
* `buildkite agents stop`
* `buildkite agents tokens create`
* `buildkite agents tokens list`
* `buildkite agents tokens remove`

buildkite teams
----------------

* `buildkite teams list`
* `buildkite teams create`
* `buildkite teams users add`
* `buildkite teams users remove`

buildkite users
----------------

* `buildkite users invite`
* `buildkite users list`
* `buildkite users remove`

buildkite aws-stack
-------------------

These commands require aws credentials either in the environment, or they will be prompted for.

* `buildkite aws-stack vpc create`
* `buildkite aws-stack vpc list`
* `buildkite aws-stack vpc remove`
* `buildkite aws-stack list`
* `buildkite aws-stack create`
* `buildkite aws-stack update`
* `buildkite aws-stack delete`
* `buildkite aws-stack env list`
* `buildkite aws-stack env upload`
* `buildkite aws-stack env download`
* `buildkite aws-stack env delete`
* `buildkite aws-stack private-key list`
* `buildkite aws-stack private-key upload`
* `buildkite aws-stack private-key download`
* `buildkite aws-stack private-key delete`
* `buildkite aws-stack link`
* `buildkite aws-stack unlink`
* `buildkite aws-stack logs follow`
* `buildkite aws-stack logs download`
* `buildkite aws-stack ssh`

The `link` command will look at your current repo and determine what provider it uses and then create a deploy key and upload it.