-
Notifications
You must be signed in to change notification settings - Fork 113
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.
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
avoid setting CI_PROJECT_ID #1168
Labels
feature
Feature missing according to gitlab ci standard
Comments
Yeah, it's probably best to just leave it undefined.
Use this one for now. |
sweet! thank you |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
gitlab-ci-local/src/predefined-variables.ts
Line 23 in 357299d
I am using CI_PROJECT_ID in scripts to
curl
the GitLab API, and it's always failing because 1217 is not correct, nor a valid id for any project.in my curl scripts i am looking up the id by searching project names. otherwise i am setting CI_PROJECT_ID myself in other projects' dotenv files within my job.
either way, it doesn't seem wise to define a variable which will never be correct
i can imagine a scenario where a blank CI_PROJECT_ID might cause problems for people, maybe we can discuss a solution for this case? but ideally we would set it to the correct id based on the full path results from
git remote origin
? and if we're offline we can use cached previous results from a file in.gitlab-ci-local/
or make it blank, or something elseThe text was updated successfully, but these errors were encountered: