---
title: Triggering Builds
description: Builds trigger automatically on git push, or manually from the dashboard. Includes debouncing and queue behavior.
---

Push to GitHub and Jamdesk builds automatically. You can also trigger builds from the dashboard.

## Automatic Builds

Every push to your connected branch triggers a build automatically:

1. You push changes to GitHub
2. GitHub sends a webhook to Jamdesk
3. Jamdesk queues and starts your build
4. Built docs deploy to the CDN

<Tip>
Builds are debounced—if you push multiple commits quickly, Jamdesk waits 10 seconds for activity to settle before building.
</Tip>

## Manual Builds

Trigger a build without pushing changes:

<Steps>
  <Step title="Open your project">
    Go to your project in the dashboard.
  </Step>
  <Step title="Go to Settings">
    Click **Settings** in the sidebar.
  </Step>
  <Step title="Click Rebuild">
    Select **Rebuild** to start a new build.
  </Step>
</Steps>

### 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

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 |

## Related Articles

<Columns cols={2}>
  <Card title="Monitoring Builds" icon="chart-line" href="/help/builds/monitoring">
    Track build progress
  </Card>
  <Card title="Build Troubleshooting" icon="wrench" href="/help/builds/troubleshooting">
    Fix common build issues
  </Card>
</Columns>