Bug in the procedure advised from ee_compat_check
Summary
A procedure advised from ee_compat_check
is wrong on that job in forked projects outside of gitlab-org/gitlab-ce.
Steps to reproduce
- Make a commit with conflicts against EE and push to start CI jobs.
- Check
ee_compat_check
job logs.
Example Project
https://gitlab.com/tnir/gitlab-ce
What is the current bug behavior?
https://gitlab.com/tnir/gitlab-ce/-/jobs/38175285:
============================================================
===================== PLEASE READ THIS =====================
============================================================
💥 Oh no! 💥
[...]
There are different ways to create such branch:
1. Create a new branch from master and cherry-pick your CE commits
# [...]
2. Apply your branch's patch to EE
# [...]
$ wget https://gitlab.com/gitlab-org/gitlab-ce/-/jobs/38175285/artifacts/raw/ee_compat_check/patches/39582-nestingdepth-6.patch
What is the expected correct behavior?
Use its namespace of that CI job not the fixed string gitlab-org
like:
$ wget https://gitlab.com/tnir/gitlab-ce/-/jobs/38175285/artifacts/raw/ee_compat_check/patches/39582-nestingdepth-6.patch
Relevant logs and/or screenshots
https://gitlab.com/tnir/gitlab-ce/-/jobs/38175285
Output of checks
This bug happens on GitLab.com.
Possible fixes
Use CI_PROJECT_URL (e.g. https://example.com/gitlab-org/gitlab-ce
) (or CI_PROJECT_PATH (e.g. gitlab-org/gitlab-ce
), CI_PROJECT_NAMESPACE (e.g. gitlab-org
)) instead of th fixed string.