Build & Deploy Lifecycle
The complete build pipeline from git push to live site: clone, validate, upload to R2, ISR revalidation, monitoring, and rollback strategies.
Push to GitHub. Jamdesk builds and deploys your docs within minutes.
Build Lifecycle
Build Triggers
| Trigger | How It Works | Use Case |
|---|---|---|
| Git Push | Webhook fires on push to connected branch | Normal development |
| Dashboard | Click "Rebuild" in project settings | Force refresh after config changes |
Builds are debounced. Commits within 10 seconds of each other go into one build.
What Happens During a Build
Jamdesk clones your repo and validates docs.json and MDX syntax. It compiles the pages to HTML with a search index. It deploys the result to Cloudflare R2. Most sites build in 30-90 seconds.
See How Jamdesk Works for the full pipeline and architecture diagram.
Deployment Status
The dashboard shows one of these statuses for each build:
| Status | Meaning |
|---|---|
| Building | Build in progress |
| Deployed | Live at your domain |
| Failed | Build error - check logs |
| Queued | Waiting for previous build |
The Build History section lists recent deployments with their status. Trigger a manual rebuild from there:
Manual Rebuild
Trigger a rebuild without pushing changes:
- Go to your project in the dashboard
- Open Settings
- Click Rebuild
Use this when:
- Fixing a stuck build
- Refreshing after platform updates
Build Logs
- Go to Deployments in your project
- Click a deployment
- Read the full build log
Common errors in the logs:
- Invalid MDX syntax
- Missing images or assets
- Broken internal links
- Configuration errors
Rollbacks
- Go to Deployments
- Find the deployment you want to restore
- Click Rollback
The previous version goes live immediately. A new build starts at the same time.
Branch Deployments
Branch deployments are available on Pro plans.
Preview changes before merging:
- Push to a feature branch
- Jamdesk creates a preview at
branch-name.your-project.jamdesk.app - Review and merge when ready