Runner Configuration
Configure GitHub Actions workflows to use Builtiful runners with the correct runs-on syntax
Runner Configuration
Learn how to configure your GitHub Actions workflows to use Builtiful's managed runners with the correct runs-on syntax.
Basic Configuration
Builtiful Runner Syntax
Builtiful uses a specific syntax format for the runs-on directive:
Simple Examples
Available Parameters
Required Parameters
| Parameter | Description | Example |
|---|---|---|
distribution | Operating system distribution | ubuntu |
Optional Parameters
| Parameter | Description | Default | Example |
|---|---|---|---|
cpus | Number of CPU cores | 2 | cpus=8 |
arch | CPU architecture | x86_64 | arch=arm64 |
Configuration Examples
CPU Scaling
Choose the right CPU count for your workload:
| CPU Count | Memory | Syntax |
|---|---|---|
| 1 | 4GB | builtiful(ubuntu, cpus=1) |
| 2 | 8GB | builtiful(ubuntu, cpus=2) |
| 3 | 12GB | builtiful(ubuntu, cpus=3) |
| 4 | 16GB | builtiful(ubuntu, cpus=4) |
| 5 | 20GB | builtiful(ubuntu, cpus=5) |
| 6 | 24GB | builtiful(ubuntu, cpus=6) |
| 7 | 28GB | builtiful(ubuntu, cpus=7) |
| 8 | 32GB | builtiful(ubuntu, cpus=8) |
| 9 | 36GB | builtiful(ubuntu, cpus=9) |
| 10 | 40GB | builtiful(ubuntu, cpus=10) |
| 11 | 44GB | builtiful(ubuntu, cpus=11) |
| 12 | 48GB | builtiful(ubuntu, cpus=12) |
| 13 | 52GB | builtiful(ubuntu, cpus=13) |
| 14 | 56GB | builtiful(ubuntu, cpus=14) |
| 15 | 60GB | builtiful(ubuntu, cpus=15) |
| 16 | 64GB | builtiful(ubuntu, cpus=16) |
Example usage:
Architecture Options
Specify CPU architecture when needed:
Complete Examples
Multi-Job Workflow
Matrix Builds
Dynamic Configuration
Pre-installed Software
All Builtiful runners include the same software as GitHub-hosted runners:
You can see the pre-installed software, as well as their versions at the GitHub Runners image release page.
Docker Support
Docker is pre-installed and running on all runners:
Service Containers
Service containers work exactly like GitHub-hosted runners:
Migration Guide
From GitHub-Hosted Runners
Before:
After:
From Self-Hosted Runners
Before:
After:
Performance Optimization
Right-Size Your Runners
| CPU Count | RAM | Use Case | Cost/Min |
|---|---|---|---|
| 2 | ~4GB | Linting, deployments, simple scripts | Lowest |
| 4 | ~8GB | Standard builds, unit tests | Low |
| 8 | ~16GB | Large projects, integration tests | Medium |
| 16 | ~32GB | Heavy compilation, parallel testing | Medium-High |
Caching Best Practices
Use GitHub's cache action for faster builds:
Troubleshooting
Common Issues
Job Stuck in Queue
Possible causes:
- Typo in runner syntax
- Invalid parameter values
- Builtiful app not installed
Check syntax:
Invalid Configuration
Common syntax errors:
Next Steps
- Review Pricing to understand costs
- Check Best Practices for optimization tips
- Read Security for compliance information
- Contact support@builtiful.io for help with configuration