Trigger downstream pipeline for database testing
What does this MR do?
We'd like to start testing database migrations automatically using large-scale data. See !51347 (merged) for context and more details around thin-cloning technology.
This change adds a CI job that triggers the downstream pipeline on the ops.gitlab.net instance. For now, this should happen
- for MRs with database migrations added
- async - this will just trigger, but not wait on the downstream pipeline.
- optional - this is allowed to fail while we're building it.
Example job: https://gitlab.com/gitlab-org/gitlab/-/jobs/984664907
Edited by Andreas Brandl