[Ops] Trigger quality gate pipelines

[delanni]

Summary

Closes: https://github.com/elastic/kibana-operations/issues/10

• chore(quality-gates): trigger downstream test pipelines from quality-gates

Issues along the way:

• Should we run the pipeline jobs FROM the pipeline.ymls, or should we trigger them?
  • Solution: triggering seems better. It can run on a different agent, so no issue with the kibana-flavored agents
• We would like to run a pipeline job IN kibana’s codebase BUT with the ci-systems pipelines. This is a problem because kibana has some scripts that assume, you’ll do something with Kibana. Now, these pipelines will just trigger other downstream jobs.
  • Solution: somehow skip the hooks if it’s not a kibana-flavored pipeline. For now, a manually set flag SKIP_KIBANA_HOOKS=1
• The pipeline can only be tested with elastic/kibana branches.
  • Solution: don’t use my mirror for this PR, at least while working on it
• The catalog-info.yaml points to a missing file ↔ the head quality-gate pipeline file is not in the right place
  • Solution: fix the catalog-info.yaml, or move the head file ✅ solved in: Qx 282 touchup qg #164643
• Missing ENVIRONMENT. Who’s going to set that variable? It’s not set at any points, the head pipeline assumes it’s present, but probably it’s not needed.
  • Solution: for now, we can add this manually
  • Question: Who/how/when will trigger this job?
• Manual testing can’t trigger certain jobs

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 6b8215e

Metrics [docs]

✅ unchanged

History

• 💚 Build #152763 succeeded 3e0e2f6b3413de05355b7b650b87e5d7fc9a1a1b

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[delanni]

Closed in favor of: #165346