Expose `CI_CONCURRENT_(PROJECT)_ID` (!1268) · Merge requests · GitLab.org / gitlab-runner · GitLab

The 17.0 major release is coming on May 16, 2024! This version brings many exciting improvements to GitLab, but also removes some deprecated features. We are introducing three breaking change windows during which we expect breaking changes to be deployed to GitLab.com. You can read more about it on our blogpost . The third breaking change window begins 2024-05-06 09:00 UTC and ends 2024-05-08 22:00 UTC.

Kamil Trzciński requested to merge expose-concurrent-id into master Mar 27, 2019

What does this MR do?

This adds support for two new runner variables:

CI_CONCURRENT_ID a unique monotic ID of job running in context of given runner (token).
CI_CONCURRENT_PROJECT_ID a unique monotic ID of job running in context of given runner (token) and project,

This is helpful to configure CI_PROJECT_ID with own unique path to be used on shared environment.

Why was this MR needed?

Make CI_PROJECT_DIR flexible enough to increase concurrency when using on shared environment.

Does this MR meet the acceptance criteria?

Documentation created/updated
Added tests for this feature/bug
In case of conflicts with master - branch was rebased

What are the relevant issue numbers?

not yet?