github.com/buildkite/agent/v3
The buildkite-agent is a small, reliable, and cross-platform build runner that makes it easy to run automated builds on your own infrastructure. It’s main responsibilities are polling buildkite.com for work, running build jobs, reporting back the status code and output log of the job, and uploading the job's artifacts.
Full documentation is available at buildkite.com/docs/agent.
$ buildkite-agent --help
Usage:
buildkite-agent <command> [options...]
Available commands are:
acknowledgements Prints the licenses and notices of open source software incorporated into this software.
start Starts a Buildkite agent
annotate Annotate the build page within the Buildkite UI with text from within a Buildkite job
annotation Make changes to an annotation on the currently running build
artifact Upload/download artifacts from Buildkite jobs
env Process environment subcommands
lock Process lock subcommands
meta-data Get/set data from Buildkite jobs
oidc Interact with Buildkite OpenID Connect (OIDC)
pipeline Make changes to the pipeline of the currently running build
step Get or update an attribute of a build step
bootstrap Run a Buildkite job locally
help Shows a list of commands or help for one command
Use "buildkite-agent <command> --help" for more information about a command.
The agent is fairly portable and should run out of the box on most supported
platforms without extras. On Linux hosts it requires dbus.
The agents page on Buildkite has personalised instructions, or you can refer to the Buildkite docs. Both cover installing the agent with Ubuntu (via apt), Debian (via apt), macOS (via homebrew), Windows and Linux.
We also support and publish Docker Images for the following operating systems. Docker images are tagged using the agent SemVer components followed by the operating system.
For example, agent version 3.45.6 is published as:
To start an agent all you need is your agent token, which you can find on your Agents page within Buildkite, and a build path. For example:
buildkite-agent start --token=<your token> --build-path=/tmp/buildkite-builds
By default, the agent sends some information back to the Buildkite mothership on
what features are in use on that agent. Nothing sensitive or identifying is sent
back to Buildkite, but if you want, you can disable this feature reporting by
adding the --no-feature-reporting flag to your buildkite-agent start call.
Features that we track can be found inside
AgentStartConfig.Features.
These instructions assume you are running a recent macOS, but could easily be adapted to Linux and Windows.
# Make sure you have Go installed.
brew install go
# Download the code somewhere - no GOPATH required.
git clone https://github.com/buildkite/agent.git
cd agent
# Create a temporary builds directory.
mkdir /tmp/buildkite-builds
# Build an agent binary and start the agent.
go build -o /usr/local/bin/buildkite-agent .
buildkite-agent start --debug --build-path=/tmp/buildkite-builds --token "abc"
# Or, run the agent directly and skip the build step.
go run *.go start --debug --build-path=/tmp/buildkite-builds --token "abc"
The latest agent version is typically compiled with the highest-numbered stable release of Go. Previous Go versions may work, but are not guaranteed to. We are using newer language features such as generics, so compiling on Go < 1.18 will fail.
We're using Go Modules to manage our Go dependencies. Dependencies are not vendored into the repository unless necessary.
The Go module published by this repo (i.e. the one you could use by adding import "github.com/buildkite/agent/v3" to your code)
is not considered to be versioned using semantic versioning. Breaking changes may be introduced in minor releases. Use
the agent as a runtime depedency of your Go app at your own risk.
We provide support for security and bug fixes on the current major release only.
Our architecture and operating system support is primarily limited by what Go itself supports.
We offer support for the following machine architectures (inspired by the Rust language platform support guidance).
We release binaries for various other platforms, and it should be possible to build the agent anywhere supported by Go, but official support is not provided for these Tier 3 platforms.
We currently provide support for running the Buildkite Agent on the following operating systems. Future minor releases may drop support for end-of-life operating systems (typically as they become unsupported by the latest stable Go release).
The agent binary is fairly portable and should run out of the box on most UNIX like systems, as well as Windows.
Many thanks to our fine contributors! You're all amazing, and we greatly appreciate your input ❤️
Copyright (c) 2014-2023 Buildkite Pty Ltd. See LICENSE for details.
See https://github.com/golang/go/issues/23011 for macOS / Go support and Supported macOS Versions for the last supported version of the Buildkite Agent for versions of macOS prior to those listed above. ↩
FAQs
Unknown package
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.