Skip to main content
Integrations connect IronBee to where your code lives and deploys. The GitHub App, the GitLab connection and the Bitbucket connection make your repositories projects, so IronBee reviews their pull requests and merge requests. IronBee also verifies your changes:
  • every deployment of an enabled project on Vercel or Netlify, with no workflow to maintain
  • every push and pull request, with the GitHub Action
  • every merge request and push to the default branch, with the GitLab component
  • every pull request and push to the main branch, with the Bitbucket Pipe
Each run exercises the change like a QA engineer would and reports the result where you already look.

The Integrations page

Owners and admins open Integrations in the console’s sidebar. The page lists the providers under Connected and Available. Select one to see its installations and the projects in each. The Integrations page with Vercel selected among GitHub, Bitbucket, Vercel and Netlify under Connected and GitLab under Available, listing two Vercel teams, each marked Nothing enabled: deployments start no runs The Integrations page with Vercel selected among GitHub, Bitbucket, Vercel and Netlify under Connected and GitLab under Available, listing two Vercel teams, each marked Nothing enabled: deployments start no runs You can connect more than one. A common setup is Vercel or Netlify for deployments, plus the GitHub App, the GitLab connection or the Bitbucket connection so the runs verify each pull request’s or merge request’s changes and report on it.

How a deployment gets verified

1

Connect the provider

Install the integration on the provider’s side and connect it to your IronBee account. Connecting needs the owner or admin role.
2

Enable projects

A Vercel or Netlify deployment starts a run only once its project is enabled with a verification type. After you connect Vercel or Netlify, the console opens the list of projects or sites to enable. Until one is enabled, the Integrations page shows Nothing enabled: deployments start no runs. Enable more later with Enable in a project’s actions menu on the provider’s page, or from Projects > New project.
3

Give IronBee access to your previews

If your previews are protected, store the way in as a secret in the project’s settings: a Vercel Bypass token or a Netlify site Password.
4

Deploy

The next deployment starts a verification run. Follow it live from Projects, and read the result on the provider, on the pull request, and in the console.

Projects and verification types

Each GitHub repository the App covers becomes an IronBee project when the App is installed; there’s nothing to enable. Each GitLab or Bitbucket repository becomes one when you pick it for its connected group or workspace, and each Vercel project or Netlify site when you enable it. A project keeps its runs, its settings and its history. Every project has a verification type:
  • Web opens the deployment in a browser and exercises it as a user would.
  • API calls the deployment over HTTP and checks the responses against its contract.
  • None starts nothing on a deployment until a type is set in the project’s settings.
A GitHub, GitLab or Bitbucket repository starts with None. Runs from the GitHub Action, the GitLab component, the Bitbucket Pipe and ironbee verify name their own type. For a Vercel project or Netlify site, pick the type when you enable it; Web is selected to start with. Change it later with Edit type on the Integrations page, or in the project’s settings. The change takes effect on the next deployment. The Enable dialog for a Vercel project, with the Web, API and None verification types and the Enable button The Enable dialog for a Vercel project, with the Web, API and None verification types and the Enable button A project can be in one of three states:

Environments, variables and secrets

A run is against one of the project’s environments, and uses that environment’s variables and secrets on top of the project-wide ones. Integrations create environments automatically, named the way the provider names the deployment: Manage them in the project’s Settings: Environments, Variables and Secrets.

Where results appear

Every run links to its verification detail page, with the recording, the actions, the network requests, traces and logs, and the result.