TestRelic AI
Go to App
Studio

Pipelines

Connect your CI provider from inside Studio — view runs and logs, trigger or cancel a run, and publish a starter workflow file.

The Pipelines tab connects Studio to your CI provider (GitHub Actions and others):

TestRelic Studioshop-e2e · Pipelines
Pipeline runs · github
RunStatusBranchCommitWhenDuration
#214runningmaina91cd02just now
#213failedfix/checkout-toaste2f7a1318m ago54s
#212successmain9b0d4411h ago48s
#211successmain77aa9f03h ago51s
Connected — runs stream into this table. Kicking off a fresh run happens via Set up in chat: the agent generates the workflow, sets secrets, and triggers run #215.
  • Connect — enter a token in the native connect dialog; it's stored locally alongside the same credentials the CLI reads.
  • Runs & logs — a live table of runs for the detected repo/branch, with logs on demand.
  • Trigger & cancel — kick off or stop a run without leaving Studio.
  • Publish a starter workflow — generate and publish a starting testrelic.yml CI workflow for the repo.

No repo yet? Publish to GitHub

If the project has no remote at all, the empty state adds a second path once GitHub is connected: Publish to GitHub (private). One click creates a new private repo under your account, wires it as origin, and pushes — then seeds the chat to generate the workflow, set the TestRelic secrets, and trigger the first run. It's the zero-repo route into CI, separate from the header Git button's own publish/sync flows. See Git integration for both.

TestRelic Studioshop-e2e · Pipelines
GitHub Actions
● connected
Pipeline runs · github
No runs yet

Connect a provider above (your token stays on this machine), then "Set up in chat" — the agent generates the workflow, sets the TestRelic secrets locally, and triggers run #1. Runs stream into this table.

This project isn't on GitHub yet — CI needs somewhere to run.

Next steps

Git integration · Workspace · Overview

Was this page helpful?

On this page