Tutorial
Configure CI/CD testing workflow
Integrate pipeline-triggered validation with the Console.
Overview
Integrate pipeline-triggered validation with the Console.
Tutorial details
- Audience
- DevOps engineer
- Duration
- 60 min
- Prerequisites
- CI/CD platform access
- Prerequisite 2
- API key
Tutorial steps
Create API key
Admin → Developer → API keys.
Navigation: Console Home quick actions or the project wizard for new initiatives. Use ⌘K / Ctrl+K to jump to any surface.
Verification: Confirm organization and team context in the Console header before making changes.
Add pipeline step
Configure trigger on push or deploy.
Navigation: Console Home quick actions or the project wizard for new initiatives. Use ⌘K / Ctrl+K to jump to any surface.
Verification: Note project, run, or agent IDs if you may need support escalation.
Validate integration
Run pipeline; confirm Console run created.
Navigation: Console Home quick actions or the project wizard for new initiatives. Use ⌘K / Ctrl+K to jump to any surface.
Verification: Confirm UI state matches your runbook. Retry once on transient errors before opening a ticket.
Policy: Store API keys in your CI secret manager, never commit credentials to source control.
Expected outcome
Pipeline triggers governed validation runs.
After completing this tutorial
- Capture run IDs and screenshots for your team runbook
- Share learnings with QA, SRE, or platform stakeholders
- Proceed to related how-to guides for operational hardening
Continue learning
Was this page helpful?
