PUBLIC ALPHABiztraak is now in public alpha. Share feedback
Biztraak
Core Concepts
Projects Components Component Settings Service Providers Deployments Domains Build Reviews Federated Apps

Build Reviews

Build Reviews provide an isolated environment for previewing and discussing a change before it is promoted. They are available only when the project, source provider, permissions, and deployment workflow support them. A commit or pull request does not universally create a review.

How Build Reviews Work

  1. Make Changes
    Create a new branch in your project and commit your updates.
    A production environment and review environments follow the branch and workflow configuration of the project.

  2. Automatic Deploy
    When the configured source and pipeline workflow triggers a review, Biztraak builds the selected revision and deploys the review environment.

  3. Preview & Share
    A review may expose deployment details or a URL through the project workflow. These outputs are not guaranteed for every component or provider.

  4. Test & Collaborate

    • Inspect logs, checks, and deployment status in the dashboard.
    • Share the review URL with teammates, stakeholders, or clients.
    • Control access using the permissions and sharing options exposed by the project workflow.

  5. Approve or Iterate

    • Promote an approved revision through the release workflow configured for the project.
    • Request changes and rerun the workflow when the source integration supports automatic rebuilds.

Key Features

  • Branch-based previews: supported source and deployment workflows can associate reviews with branches or revisions
  • Faster collaboration: designers, QA, and PMs can test live apps without local setup
  • Access control: review visibility follows the permissions and sharing settings exposed by the workflow
  • Deployment insights: view build info, summaries, checks, and domain assignments
  • Operational context: logs, checks, and audit records are available when emitted by the selected workflow

Example Workflow

  1. A developer creates or updates a revision accepted by the project’s source workflow.
  2. The configured pipeline creates a review and reports its build or deployment state.
  3. Reviewers inspect the available preview, logs, and checks.
  4. The team approves, updates, or removes the review according to the configured lifecycle.

Next steps

Build Reviews give teams a review environment where the configured project workflow can be evaluated before a change is merged or promoted. A review environment is not a guarantee that production will behave identically. Provider, data, secrets, and runtime differences still matter.