Proposal: Trigger GDK as Gitlab downstream pipeline when critical dependency versions change that could impact GDK

Objective

We would like to introduce an early feedback when changes made in the GitLab project may potentially impact GDK.

Examples where GitLab merge requests can break GDK: [fill in this section with some ]

Proposal

When code changes occur in the following areas, we kick off the GDK pipeline as a downstream pipeline:

• Gemfiles
• db migrations
• VERSION changes
  1. VERSION
  2. GITALY_SERVER_VERSION
  3. GITLAB_SHELL_VERSION
  4. etc...

Gotchas

• the GDK image used in this downstream pipeline doesn't have to be built from scratch. We can make some assumptions about where we start with GDK so Caching is acceptable.

• GDK should be using the merged results commit from the merge request. This means we cannot just fetch from the branch, but instead fetch from the commit of the pipeline.