Triggers new Buildkite builds with branch/commit control and safety confirmations.
Trigger new Buildkite builds with appropriate safety checks.
| Tool | Purpose |
|---|---|
get_pipeline | Verify pipeline exists and get details |
list_pipelines | List all pipelines in the organization |
create_build | Trigger a new build |
list_builds | Check recent builds (optional) |
Parse from $ARGUMENTS or user's message:
| Input Format | Example |
|---|
| Pipeline name | my-pipeline |
| Pipeline + branch | my-pipeline on main |
| Description | "the deploy pipeline" |
| Rebuild request | "rebuild build 123" |
Identify the pipeline
buildkite_get_pipeline to verifyDetermine parameters
Confirm before triggering
Create the build with buildkite_create_build
Report result
I'll trigger a build for **my-org/my-pipeline**:
- Branch: `main`
- Commit: `abc123` (latest)
Proceed? (yes/no)
If pipeline name contains: deploy, prod, production, release
⚠️ This appears to be a deployment pipeline.
I'll trigger **my-org/deploy-production**:
- Branch: `main`
- Commit: `abc123`
This may deploy to production. Please confirm by typing "deploy" to proceed.
If setting env vars, show them clearly:
Build will include these environment variables:
- DEPLOY_ENV=staging
- SKIP_TESTS=true
Proceed?
| Parameter | Source | Default |
|---|---|---|
| branch | User input, git context | Ask user |
| commit | Usually "HEAD" | Latest on branch |
| message | Optional | Auto-generated |
| env | User-specified | None |
After triggering:
✅ Build triggered successfully!
**Build #457**: https://buildkite.com/my-org/my-pipeline/builds/457
- Branch: main
- Commit: abc123
- Status: scheduled
The build is now queued and will start when an agent is available.
User: Run CI on my branch
1. Identify pipeline (from context or ask)
2. Get current git branch
3. Confirm: "Trigger my-pipeline on feature-branch?"
4. On confirmation, create build
5. Return build URL and status