diff options
| author | Patrick Steinhardt <psteinhardt@gitlab.com> | 2021-04-21 15:31:19 +0300 |
|---|---|---|
| committer | Patrick Steinhardt <psteinhardt@gitlab.com> | 2021-04-29 13:19:41 +0300 |
| commit | 96ae0699d3d939d9fde300c29d20d60fb0641a20 (patch) | |
| tree | 87d3697953d00dd63694f502db7ad21f33a42d70 /.gitlab-ci.yml | |
| parent | 08a0862854886c544c4d0310b3c2b9800af5ddc6 (diff) | |
ci: Add manual job to trigger QA
It's currently more complicated than necessary to trigger a QA run with
changes which are currently in review. As a result, we tend to just not
bother and wait for QA to crash at a later stage, when changes had been
merged to the master branch already and when GitLab is about to bump the
Gitaly server version. While we certainly don't want all MRs to be
tested by QA, it would be reasonable to do so for MRs which e.g.
deprecate existing features or which implement significant changes like
for example the recent Go ports.
Improve the situation by adding a new manual "qa" job. If executed, then
it triggers a QA pipeline with the tip of the MR as Gitaly server
version.
Diffstat (limited to '.gitlab-ci.yml')
| -rw-r--r-- | .gitlab-ci.yml | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 187a2158f..50d2e951a 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -2,6 +2,7 @@ stages: - build - test - publish + - qa default: image: registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7-golang-1.15-git-2.31 @@ -300,3 +301,12 @@ code_navigation: artifacts: reports: lsif: dump.lsif + +trigger-qa: + stage: qa + when: manual + trigger: + project: gitlab-org/build/omnibus-gitlab-mirror + variables: + ALTERNATIVE_SOURCES: "true" + GITALY_SERVER_VERSION: $CI_COMMIT_SHA |