job name limitations documentation
I am wondering if https://docs.gitlab.com/ee/ci/jobs/#job-name-limitations is still accurate?
I am able to run such a pipeline without any issues: https://gitlab.com/hverlin/gitlab-ci-local-tests/-/pipelines/1329066119
types:
script:
- echo "test"
test:
needs: [types]
script:
- echo "test"
"true":
script:
- echo "test"
"false":
script:
- echo "test"
"nil":
script:
- echo "test"
I have personally seen developers creating a job named types
(e.g., to generate typescript
types definition).
Does this limitation still apply?
Implementation details
- Update the schema to prevent
cache
,true
andfalse
as job names, so they get underlined as invalid in the editor, not just the pipeline validation.* Removetypes
from the list, because I agree that this should be fine now.types
is the old name forstages
, which has been removed for a long time now. - Double check with @avielle about
nil
, as it doesn't seem to be flagging as invalid, despite: Avoid exceptions from un-symbolizable jobs (!80417 - merged)
Edited by Dov Hershkovitch