Skip to content

E2E test: run gdk tests with gitaly transactions for Gitaly version changes

Jay McCure requested to merge jmc-gitaly-trans-gdk into master

What does this MR do and why?

Resolves gitlab-org/quality/quality-engineering/team-tasks#3041 (comment 2140498134)

  • Runs the gdk tests with gitaly transactions enabled when there is a change to the gitaly version
  • The tests run in parallel to the gdq-qa-blocking tests and they are also blocking. They don't run in scheduled pipelines.
  • Small adjustment to how we start gdk, so we have the logs for gdk start

Screenshot_2024-10-03_at_10.49.58

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.

How to set up and validate locally

Pipeline only change

Example pipelines

Example log

We can see that transactions are enabled from this message:

2024-10-02_06:39:23.38177 [35mgitaly                : [0m{"level":"warning","msg":"Transactions enabled. Transactions are an experimental feature. The feature is not production ready yet and might lead to various issues including data loss.","pid":4550,"time":"2024-10-02T06:39:23.381Z"}

Which is present in https://gitlab.com/gitlab-org/gitlab/-/jobs/7971595467/artifacts/external_file/gdk.gitaly.log (transactions enabled) and absent in https://gitlab.com/gitlab-org/gitlab/-/jobs/7971595417/artifacts/external_file/gdk.gitaly.log (default config)

Edited by Jay McCure

Merge request reports

Loading