How-to Guide
Configure CI/CD
Trigger governed validation from your deployment pipeline.
Objective
Trigger governed validation from your deployment pipeline.
Prerequisites
- Integration configured
- API key or token
Procedure
Generate API credentials
Admin Center → 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 GitHub Actions, GitLab CI, or Jenkins per docs.
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 trigger
Run pipeline and 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.
Verification checklist
- Confirm expected UI state or API response after each critical step
- Document run ID, project ID, or agent ID for support escalation if needed
- Notify stakeholders if the workflow affects release gates or production validation
Expected result
Pipeline triggers validation runs on configured events.
Was this page helpful?
