Change to multi-project pipelines for RAT triggers
What does this MR do?
Change to multi-project pipelines for RAT triggers
- RAT triggers from merge requests now use multi-project pipelines
- Add RAT trigger variables to facts
- Update documentation for variables when using RAT pipelines
Closes https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7191
Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>
Instead of using a trigger token, use multi-project pipelines for RAT triggers from MR pipelines. Note that this doesn't touch the nightly or tag triggers, as they are from dev.gitlab.org to gitlab.com
Related issues
Closes: #7191 (closed)
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion
Required
-
Merge Request Title, and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks -
trigger-package
has a green pipeline running against latest commit
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Tests added -
Integration tests added to GitLab QA -
Equivalent MR/issue for the GitLab Chart opened
Edited by Robert Marshall