Skip to content
Snippets Groups Projects
Commit f036a324a62e authored by Georges Racinet's avatar Georges Racinet
Browse files

Taking GitLab repo description from GL_REPOSITORY

We make `GL_REPOSITORY` the norm to describe the repo in
GitLab terms:

- in `wsgi.py`, we now expect to receive it from Heptapod Workhorse,
  matching changes done there right after the merge with the version
  for GitLab 12.3.5. In the subprocess call case (gitlab-shell or
  Rails app), we already had it.
- instead of hardcoding `project-$id` to pass it to GitLab API
  endpoints, which was too restrictive, we just repass it over
- we still produce a `HEPTAPOD_PROJECT_ID` environment variable
  for external Mercurial hooks, but now we derive it from
  GL_REPOSITORY
parent 94c6158b3bfa
No related branches found
No related tags found
Loading
Checking pipeline status
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment