Add downstream observability e2e trigger to ci
What does this MR do and why?
Add downstream observability e2e trigger to CI
This manual trigger job will run the gitlab-org/opstrace/opstrace pipeline where the observability e2e tests live. It must be run manually when the MR author chooses.
This trigger will only be available on MRs and there must be a corresponding branch in https://gitlab.com/gitlab-org/opstrace/opstrace with the same name as the MR branch. This is for 2 reasons:
- e2e tests live in https://gitlab.com/gitlab-org/opstrace/opstrace and we need a way to develop/alter tests in relation to an MR in this repo.
- I explored the idea of defaulting the branch in https://gitlab.com/gitlab-org/opstrace/opstrace to main, and then allowing the user to override this with a CICD variable when they manually run the job. This began to get complicated because trigger-jobs don't directly allow a user to specify CICD variables when manually triggering them.
To run these tests, just create and push a branch to https://gitlab.com/gitlab-org/opstrace/opstrace with the same name as the branch in the https://gitlab.com/gitlab-org/gitlab MR. Any edits to tests can then be done on that branch in https://gitlab.com/gitlab-org/opstrace/opstrace. In many cases, no changes will be made to the tests in the https://gitlab.com/gitlab-org/opstrace/opstrace branch, however if changes are made then once the MR in https://gitlab.com/gitlab-org/gitlab merges, the corresponding MR in https://gitlab.com/gitlab-org/opstrace/opstrace can be merged.
Example below of the new job:
This job was manually triggered by the "play" button and succeeded, reporting back the status from the child pipeline in https://gitlab.com/gitlab-org/opstrace/opstrace.
Before triggering this job, I created and pushed a branch to https://gitlab.com/gitlab-org/opstrace/opstrace called mappelman/downstream-trigger-gob-e2e (same as this MR) which was used to run the child pipeline. This branch contains the changes present in gitlab-org/opstrace/opstrace!2357 (merged) which allow this to work.
Signed-off-by: Mat Appelman mappelman@gitlab.com
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.