Releases: buildkite/agent
Releases · buildkite/agent
v1.0-beta.6
- The first official Windows beta
v1.0-beta.5
- The S3 Uploader can now use the EC2 instance meta data keys for uploading files
v1.0-beta.4
- $BUILDBOX_DIR can now be overridden in
bootstrap.sh - $BUILDBOX_BIN_DIR is injected into the ENV by the agent, and is set to the folder where the
buildbox-agentbinary is being run from
v1.0-beta.3
- Starting experimenting with Windows support
buildbox-agent build-meta-datahas been renamed to:buildbox-agent build-databuildbox-agent artifacthas been renamed to:buildbox-agent build-artifact- The
--urlparameter has been renamed to--endpointand the ENV variableBUILDBOX_AGENT_ENDPOINT - No longer add
EC2=trueif you're using--meta-data-ec2-tags - Fixed places where the agent should disconnect
v1.0-beta.2
- The new combined binary is:
~/.buildbox/bin/buildbox-agent - Updated CLI method names:
buildbox agent start=>buildbox-agent startbuildbox artifact upload ...=>buildbox-agent artifact upload ...buildbox data set ...=>buildbox-agent build-meta-data set ...
- Included a
--no-ptyoption - Agents can now set a priorty with
--priority - Meta data can automatically be filled with EC2 tags by using:
--meta-data-ec2-tags - Jobs are now accepted before running
- Don't show
io.Copyerrors when they're expected - The agent now reports it's
PIDto Buildbox - Sending a
USR1signal to the agent will cause it to dump debugging information into the log
v1.0-beta.1
- Combined
buildbox-agent,buildbox-artifactand ``buildbox-data` into 1 binary. - Agents can now be started with the
--tokenparameter that allows agents to be created on the fly - Agents now send a disconnect signal to Buildbox when they shut down
- Deprecated use of --access-token when starting an agent. It must be started with your account agent token instead.
v0.2
v0.2-beta.13
- Tweaked what gets logged when downloading artifacts
v0.2-beta.12
- Added basic support for downloading artifacts:
buildbox-artifact download "pkg/*" .
v0.2-beta.11
- Artifacts are uploaded with relative paths, instead of absolute. This was always the intention, but was lost in the rewrite form ruby -> golang.