Tracera
Start trial

Integrations

Connect CI pipelines so Run and Rerun can start builds on your providers from Tracera.

Project settings Integrations with CI pipelines
Integrations: pipelines under Project settings, with Add to connect a provider.

Before you start

  1. Open Project settings → Integrations (you need project settings access).
  2. Store a project Autotest token in your CI secrets — see Tokens. Tracera does not send that token when it starts a pipeline.
  3. Use an adapter that reports with TRACERA_TEST_RUN_ID set — see Adapters.

How it works

  1. Under Integrations, choose Add and pick a provider.
  2. Fill the Pipeline, Connection, and optional Params tabs, then save.
Add GitHub Actions pipeline modal with Pipeline Connection Params tabs
Add a pipeline: Pipeline, Connection, and optional Params.
  1. When you Run or Rerun and the project has pipelines, Tracera opens the Run in CI dialog. Select up to 10 pipelines (pre-checked ones follow Default).
Run in CI dialog with pipeline checkboxes
Run in CI: after you run or rerun, choose up to 10 pipelines — those with Default on are checked.
  1. Tracera creates the run, then triggers the selected pipelines. It always sends TRACERA_TEST_RUN_ID, TRACERA_BASE_URL, and TRACERA_PROJECT_ID (UI overrides for those keys are ignored). Custom params from the pipeline are included. The Autotest Bearer is not sent.
  2. In CI, map those values into the job environment, keep the Autotest token in secrets, and report with an adapter with TRACERA_TEST_RUN_ID set.

Pipelines can share a connection. Updating the token on that connection updates every pipeline that uses it.

Providers

GitHub Actions

Pipeline: Repository (owner/repo), Workflow file (for example e2e.yml), Branch or tag. Optional Server URL (empty = api.github.com).

Declare TRACERA_TEST_RUN_ID, TRACERA_BASE_URL, TRACERA_PROJECT_ID, and any custom params as workflow_dispatch inputs in the workflow file. Otherwise GitHub rejects unexpected inputs.

Jenkins

Pipeline: Job URL (must include /job/… segments). Connection: Username and API token, plus the server from the job URL.

GitLab CI

Pipeline: GitLab project (path group/project or numeric id) and Branch or tag. Optional Server URL (empty = gitlab.com).

TeamCity

Pipeline: Build type id. Connection: Server URL (required) and token.

Azure Pipelines

Pipeline: Organization, Azure project, Pipeline id, and Branch. Optional Server URL (empty = dev.azure.com).

Related: Project settings, Tokens, Adapters.