Inconsistent behaviour of variables when using with GitLab CI
abhisheksaxena7 opened this issue ยท comments
Abhishek Saxena commented
Bug
While using env-ci with GitLab I found a possible bug in the usage of GitLab variables.As per the env-ci documentation:
build: CI service build number
job: CI service job number
slug: The slug (in form: owner_name/repo_name) of the repository currently being built.
which according to GitLab Doc correspond to:
build: CI_PIPELINE_ID
job: CI_JOB_ID
slug: CI_PROJECT_PATH_SLUG
Right now they correspond to:
build: CI_JOB_NAME -
job: CI_JOB_STAGE -
slug: CI_PROJECT_PATH -
Environment:
- CI: GitLab
Support variable
Documentation:
Pierre Vanduynslager commented
๐ This issue has been resolved in version 1.7.1 ๐
The release is available on:
Your semantic-release bot ๐ฆ๐