buildkite is a free and open-source CI agent. Buildkite provides on-premises agents for CI/CD pipelines
1. Prerequisites
2. Supported Operating Systems
This guide supports installation on:
3. Installation
RHEL/CentOS/Rocky Linux/AlmaLinux
# Install EPEL repository if needed
sudo dnf install -y epel-release
# Install buildkite
sudo dnf install -y buildkite
# Enable and start service
sudo systemctl enable --now buildkite
# Configure firewall
sudo firewall-cmd --permanent --add-port=N/A/tcp
sudo firewall-cmd --reload
# Verify installation
buildkite --version
Debian/Ubuntu
# Update package index
sudo apt update
# Install buildkite
sudo apt install -y buildkite
# Enable and start service
sudo systemctl enable --now buildkite
# Configure firewall
sudo ufw allow N/A
# Verify installation
buildkite --version
Arch Linux
# Install buildkite
sudo pacman -S buildkite
# Enable and start service
sudo systemctl enable --now buildkite
# Verify installation
buildkite --version
Alpine Linux
# Install buildkite
apk add --no-cache buildkite
# Enable and start service
rc-update add buildkite default
rc-service buildkite start
# Verify installation
buildkite --version
openSUSE/SLES
# Install buildkite
sudo zypper install -y buildkite
# Enable and start service
sudo systemctl enable --now buildkite
# Configure firewall
sudo firewall-cmd --permanent --add-port=N/A/tcp
sudo firewall-cmd --reload
# Verify installation
buildkite --version
macOS
# Using Homebrew
brew install buildkite
# Start service
brew services start buildkite
# Verify installation
buildkite --version
FreeBSD
# Using pkg
pkg install buildkite
# Enable in rc.conf
echo 'buildkite_enable="YES"' >> /etc/rc.conf
# Start service
service buildkite start
# Verify installation
buildkite --version
Windows
# Using Chocolatey
choco install buildkite
# Or using Scoop
scoop install buildkite
# Verify installation
buildkite --version
Initial Configuration
Basic Configuration
# Create configuration directory
sudo mkdir -p /etc/buildkite
# Set up basic configuration
# See official documentation for detailed configuration options
# Test configuration
buildkite --version
5. Service Management
systemd (RHEL, Debian, Ubuntu, Arch, openSUSE)
# Enable service
sudo systemctl enable buildkite
# Start service
sudo systemctl start buildkite
# Stop service
sudo systemctl stop buildkite
# Restart service
sudo systemctl restart buildkite
# Check status
sudo systemctl status buildkite
# View logs
sudo journalctl -u buildkite -f
OpenRC (Alpine Linux)
# Enable service
rc-update add buildkite default
# Start service
rc-service buildkite start
# Stop service
rc-service buildkite stop
# Restart service
rc-service buildkite restart
# Check status
rc-service buildkite status
rc.d (FreeBSD)
# Enable in /etc/rc.conf
echo 'buildkite_enable="YES"' >> /etc/rc.conf
# Start service
service buildkite start
# Stop service
service buildkite stop
# Restart service
service buildkite restart
# Check status
service buildkite status
launchd (macOS)
# Using Homebrew services
brew services start buildkite
brew services stop buildkite
brew services restart buildkite
# Check status
brew services list | grep buildkite
Windows Service Manager
# Start service
net start buildkite
# Stop service
net stop buildkite
# Using PowerShell
Start-Service buildkite
Stop-Service buildkite
Restart-Service buildkite
# Check status
Get-Service buildkite
Advanced Configuration
See the official documentation for advanced configuration options.
Reverse Proxy Setup
nginx Configuration
upstream buildkite_backend {
server 127.0.0.1:N/A;
}
server {
listen 80;
server_name buildkite.example.com;
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl http2;
server_name buildkite.example.com;
ssl_certificate /etc/ssl/certs/buildkite.example.com.crt;
ssl_certificate_key /etc/ssl/private/buildkite.example.com.key;
location / {
proxy_pass http://buildkite_backend;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
Apache Configuration
<VirtualHost *:80>
ServerName buildkite.example.com
Redirect permanent / https://buildkite.example.com/
</VirtualHost>
<VirtualHost *:443>
ServerName buildkite.example.com
SSLEngine on
SSLCertificateFile /etc/ssl/certs/buildkite.example.com.crt
SSLCertificateKeyFile /etc/ssl/private/buildkite.example.com.key
ProxyRequests Off
ProxyPreserveHost On
ProxyPass / http://127.0.0.1:N/A/
ProxyPassReverse / http://127.0.0.1:N/A/
</VirtualHost>
HAProxy Configuration
frontend buildkite_frontend
bind *:80
bind *:443 ssl crt /etc/ssl/certs/buildkite.pem
redirect scheme https if !{ ssl_fc }
default_backend buildkite_backend
backend buildkite_backend
balance roundrobin
server buildkite1 127.0.0.1:N/A check
Security Configuration
Basic Security Setup
# Set appropriate permissions
sudo chown -R buildkite:buildkite /etc/buildkite
sudo chmod 750 /etc/buildkite
# Configure firewall
sudo firewall-cmd --permanent --add-port=N/A/tcp
sudo firewall-cmd --reload
# Enable SELinux policies (if applicable)
sudo setsebool -P httpd_can_network_connect on
Database Setup
See official documentation for database configuration requirements.
Performance Optimization
System Tuning
# Basic system tuning
echo 'net.core.somaxconn = 65535' | sudo tee -a /etc/sysctl.conf
echo 'net.ipv4.tcp_max_syn_backlog = 65535' | sudo tee -a /etc/sysctl.conf
sudo sysctl -p
Monitoring
Basic Monitoring
# Check service status
sudo systemctl status buildkite
# View logs
sudo journalctl -u buildkite -f
# Monitor resource usage
top -p $(pgrep buildkite)
9. Backup and Restore
Backup Script
#!/bin/bash
# Basic backup script
BACKUP_DIR="/backup/buildkite"
DATE=$(date +%Y%m%d_%H%M%S)
mkdir -p "$BACKUP_DIR"
tar -czf "$BACKUP_DIR/buildkite-backup-$DATE.tar.gz" /etc/buildkite /var/lib/buildkite
echo "Backup completed: $BACKUP_DIR/buildkite-backup-$DATE.tar.gz"
Restore Procedure
# Stop service
sudo systemctl stop buildkite
# Restore from backup
tar -xzf /backup/buildkite/buildkite-backup-*.tar.gz -C /
# Start service
sudo systemctl start buildkite
6. Troubleshooting
Common Issues
1. Service won't start:
# Check logs
sudo journalctl -u buildkite -n 100
sudo tail -f /var/log/buildkite/buildkite.log
# Check configuration
buildkite --version
# Check permissions
ls -la /etc/buildkite
2. Connection issues:
# Check if service is listening
sudo ss -tlnp | grep N/A
# Test connectivity
telnet localhost N/A
# Check firewall
sudo firewall-cmd --list-all
3. Performance issues:
# Check resource usage
top -p $(pgrep buildkite)
# Check disk I/O
iotop -p $(pgrep buildkite)
# Check connections
ss -an | grep N/A
Integration Examples
Docker Compose Example
version: '3.8'
services:
buildkite:
image: buildkite:latest
ports:
- "N/A:N/A"
volumes:
- ./config:/etc/buildkite
- ./data:/var/lib/buildkite
restart: unless-stopped
Maintenance
Update Procedures
# RHEL/CentOS/Rocky/AlmaLinux
sudo dnf update buildkite
# Debian/Ubuntu
sudo apt update && sudo apt upgrade buildkite
# Arch Linux
sudo pacman -Syu buildkite
# Alpine Linux
apk update && apk upgrade buildkite
# openSUSE
sudo zypper update buildkite
# FreeBSD
pkg update && pkg upgrade buildkite
# Always backup before updates
tar -czf /backup/buildkite-pre-update-$(date +%Y%m%d).tar.gz /etc/buildkite
# Restart after updates
sudo systemctl restart buildkite
Regular Maintenance
# Log rotation
sudo logrotate -f /etc/logrotate.d/buildkite
# Clean old logs
find /var/log/buildkite -name "*.log" -mtime +30 -delete
# Check disk usage
du -sh /var/lib/buildkite
Additional Resources
---
Note: This guide is part of the HowToMgr collection. Always refer to official documentation for the most up-to-date information.