What a legacy trigger is
A legacy trigger belongs to one environment, and there is no workspace-wide list of them — each environment carries its own. Covering staging and production means one trigger in each. Legacy triggers come in three kinds:- Scheduled — runs the environment’s flows on a repeating interval.
- Deployment — runs them when your pipeline reports a deploy that matches the trigger’s deployment type and branch scope.
- Pull-request button — runs them when someone presses the testing button on a pull request.
How deploys reach a legacy trigger
A legacy deployment trigger fires on one of two arrival paths:- The
deploy_successendpoint — reached directly, through@qawolf/ci-sdk, or through the notify-on-deploy GitHub Action. All three are the same endpoint. See webhooks/deploy_success for the request and response. - GitHub or GitLab deployment events — forwarded by the connected code host integration.
Which flows a legacy trigger runs
A legacy trigger runs the flows carrying its tags, or every flow in its environment when it has no tags. Some deployment triggers instead use adaptive flow selection, where QA Wolf picks the flows from the pull request the deploy belongs to.In this section
- GitHub Actions and GitLab CI — notifying QA Wolf from the pipeline that deploys.
- Setting up PR testing on GitHub and on GitLab.
- Node.js SDK, Webhook and CircleCI — reporting a deploy from a pipeline QA Wolf’s code host integrations do not cover.