pipeline-run

To trigger a QA pipeline run from a Jira ticket, you provide a Jira ticket key matching the NAA-\d+ format in your message. The pipeline parses the ticket key and routes the request through the QA orchestrator for execution.

Ticket-driven QA orchestration coordinates end-to-end pipeline execution triggered by a Jira ticket key. It routes the run through a QA orchestrator and captures post-execution learning artifacts, storing the results under pipeline-logs.

You do not need to specify an environment when starting a training pipeline run. The environment parameter is optional and defaults to master if omitted, while optional credentials can also be provided during input extraction.

Yes, you can use this orchestrator to simulate pipeline cycles in training mode without affecting real test runs. It coordinates sub-agents to guide post-execution learning steps, error handling, and escalation flows safely.

The Jira ticket key format matters because the pipeline automation specifically parses for keys matching the NAA-\d+ pattern. Without a valid ticket key, the system cannot extract the necessary input to route the run through the QA orchestrator.

When running hands-off QA pipeline training cycles, expect limitations tied to the QA orchestrator contract and sub-agent coordination. The system focuses on training simulation and learning capture, safeguarding real test runs rather than executing production deployments.