BUGDROP.
    BUILDS

    Builds & Previews

    BugDrop runs your code in isolated build workers. Every push or manual trigger creates an immutable build artifact and a unique preview URL.

    BUILD LIFECYCLE

    Every build moves through a strict 5-step pipeline. The timeline gives you real-time visibility into the current build phase.

    Build Queued

    10:00:00 AMCompleted

    Waiting for available worker.

    Initialize Environment

    10:00:05 AMCompleted

    Cloning repository and setting up build container.

    Install Dependencies

    10:00:15 AMActive

    Running package manager install command.

    Build Application

    Pending

    Executing framework build script.

    Deploy Output

    Pending

    Uploading static assets to edge network.

    BUILD STATUSES

    The overall state of a build.

    Queued
    Waiting for a build slot to become available
    Building
    Clone, install, and build in progress
    Success
    Build completed — preview is live
    Failed
    Build failed — check the build logs
    Cancelled
    Manually cancelled before completion

    BUILD LOG VIEWER

    Real-time logs streamed directly from the build worker. Lines are automatically parsed into severity levels (info, success, warn, error).

    Acme Web App — main — bld_01HZ...
    Building
    110:00:05 Cloning repository github.com/acmecorp/web...
    210:00:06✔Repository cloned successfully in 1.2s
    310:00:07 Restoring cache from previous build...
    410:00:09 Running install command: pnpm install
    510:00:12 Lockfile is up to date, resolution step is complete
    610:00:15✔Dependencies installed in 6.4s
    710:00:16 Running build command: pnpm run build
    810:00:17 > next build
    910:00:22▲▲ warn - Invalid next.config.js options detected.
    1010:00:35 ✓ Compiled successfully
    1110:00:36 Deploying to edge network...
    running…

    EMBEDDED OUTPUT

    When viewing build failures from the dashboard or side panels, a simplified CodeBlock is often used.

    bash
    [system]   ◉ Cloning repo: acmecorp/web-app
    [stdout]   > next build
    [stdout]   Creating an optimized production build...
    [stderr]   Failed to compile.
    [stderr]   ./src/app/page.tsx
    [stderr]   Module not found: Can't resolve '@/components/ui/button'

    LIMITS, RETRIES & CACHE

    Build timeout
    Long-running builds are terminated at the platform timeout. If you hit this repeatedly, optimize the install/build pipeline.
    Retry behavior
    Failed builds can be manually retried from the builds panel. Retries create a new immutable build ID.
    Cache usage
    Dependency/build cache is restored automatically when available and refreshed on successful builds.
    Cancellation
    Cancelled builds stop immediately and do not publish a preview artifact.