Triggering Builds
Builds trigger automatically on git push, or manually from the dashboard and API. Includes debouncing and queue behavior.
Push to GitHub and Jamdesk builds automatically. You can also trigger builds from the dashboard or API.
Automatic Builds
Every push to your connected branch triggers a build automatically:
- You push changes to GitHub
- GitHub sends a webhook to Jamdesk
- Jamdesk queues and starts your build
- Built docs deploy to the CDN
Builds are debounced—if you push multiple commits quickly, Jamdesk waits 10 seconds for activity to settle before building.
Manual Builds
Trigger a build without pushing changes:
Go to your project in the dashboard.
Click Settings in the sidebar.
Select Rebuild to start a new build.
When to Use Manual Builds
- After changing environment variables
- To refresh after a failed build
- After Jamdesk platform updates
- To clear cached content
API Builds
Trigger builds programmatically for CI/CD integration:
curl -X POST "https://api.jamdesk.com/projects/YOUR_PROJECT_ID/rebuild" \
-H "Authorization: Bearer YOUR_API_KEY"Find your API key in Settings → API.
For full authentication, error handling, and rate limit guidance, see Builds API / Triggers.
Build Queue
During high traffic, builds may queue briefly. Queue position shows in the dashboard. Builds process in order received.
Concurrent Builds
Each project can have one build running at a time. New triggers while a build is running will queue.
| Plan | Concurrent Projects |
|---|---|
| Trial | 1 |
| Pro | 3 |