Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider using CI_PIPELINE_IID for gitlab #34

Closed
joshfriend opened this issue Mar 27, 2019 · 1 comment
Closed

Consider using CI_PIPELINE_IID for gitlab #34

joshfriend opened this issue Mar 27, 2019 · 1 comment

Comments

@joshfriend
Copy link

CI_PIPELINE_ID is shared between all projects and will increase very rapidly if you have lots of projects and builds, whereas CI_PIPELINE_IID is:

The unique id of the current pipeline scoped to project

Some caveats:

  • CI_PIPELINE_IID is only available for gitlab v11.0 and higher
  • Anyone currently using the other CI_PIPELINE_ID will be unable to just switch over because that would cause the build number to decrease.
@jdouglas-nz
Copy link
Collaborator

@joshfriend - I'll patch this in! I'll have it return the CI_PIPELINE_IID , if it is present, or alternatively fall back to the CI_JOB_ID (which is what it does currently)

@joshfriend
Copy link
Author

#40

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@joshfriend @jdouglas-nz