Triggering Builds
Builds trigger automatically on git push, or manually from the dashboard. Includes debouncing and queue behavior.
Jamdesk builds your docs on every push to GitHub. You can also trigger a build from the dashboard.
Automatic Builds
Every push to your connected branch triggers a build:
- 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. Jamdesk waits until 10 seconds pass with no new push, then builds.
Manual Builds
Trigger a build without pushing changes:
1
Open your projectGo to your project in the dashboard.
2
Go to SettingsClick Settings in the sidebar.
3
Click RebuildSelect Rebuild. A new build starts.
When to Use Manual Builds
- After changing environment variables
- To refresh after a failed build
- After Jamdesk platform updates
- To clear cached content
Build Queue
Builds may queue briefly during high traffic. The dashboard shows queue position. Builds run in the order received.
Concurrent Builds
Each project runs one build at a time. A trigger that arrives during a running build waits in the queue.
| Plan | Concurrent Projects |
|---|---|
| Trial | 1 |
| Pro | 3 |