BSD Portsdevel/buildkite-agent 3.95.0 DragonFly
Cross-platform build runner to run your own build tasks
- System
- DragonFly
- Repository
- DPorts
- Maintainer
- [email protected] (as in FreeBSD)
- License
- APACHE20, BSD2CLAUSE, BSD3CLAUSE, LGPL3, MIT
- Categories
- devel, sysutils
- Package size
- 9568.2 KiB, 41933.2 KiB installed
Description
Buildkite-agent is a small, reliable, and cross-platform build runner that makes it easy to run automated builds on your own infrastructure. Its 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.
In the other systems
The newest version among them is 3.138.0, as upstream numbers it.
| System | Port | Version | Vulnerabilities | Status | Maintainer | Last update |
|---|---|---|---|---|---|---|
| DragonFly | devel/buildkite-agent | 3.95.0 behind since 2026-10-08 | none known | - | [email protected] | - |
| FreeBSD | devel/buildkite-agent | 3.138.0_2 newest | none known | - | [email protected] | 2026-10-20 |
| HardenedBSD | devel/buildkite-agent | 3.124.0_6 behind since 2026-10-08 | no data | - | [email protected] | - |
| GhostBSD | devel/buildkite-agent | 3.124.0_6 behind since 2026-10-08 | no data | - | [email protected] | - |
Install
Binary package:
pkg install buildkite-agentFrom DPorts:
cd /usr/dports/devel/buildkite-agent && make install cleanDependency graph
Ports that need it on the left, what it needs to run on the right; at most 8 of each. "Dependencies" below lists them all.
Dependencies
Run dependencies 1
No port depends on this one.
Configuration
No options to configure.
- Service scripts
- none
Message after installing
buildkite-agent requires minimal configuration in rc.conf, to allow hiding the the agent token from casual prying eyes, and to specify the user account to run the agent under, as its home directory is needed for ssh keys and agents, source code repositories, and temporary build worksapces. The /usr/local/rc.conf.d/buildkite file should be protected via owner/group root:wheel and 0600 permissions, to ensure the API token is not left exposed to non-privileged users and to any processes the agent itself may launch. Note: the supplied user must have full filesystems permissions over its homedir. # /usr/local/rc.conf.d/buildkite # mandatory parameters buildkite_enable=YES buildkite_token=abc123456def buildkite_account=sudo_make_me_a_user # optional parameters buildkite_config=/usr/local/etc/buildkite/buildkite-agent.cfg buildkite_vars="KEY=value MORE=values" See https://buildkite.com/docs/agent for further details.