Pipeline not triggered when job name is too long
Summary
When a job has a long name (for example 453 characters), then pipelines are not triggered.
Steps to reproduce
- Create a blank project
- Add a basic gitlab-ci.yml file with a single job
- Ensure that the job triggers pipelines successfully
- Modify the job name to make it very long (several hundred characters)
- Pipelines will no longer be triggered for this job
Example Project
https://gitlab.com/anazir-group/long-job-names
What is the current bug behavior?
GitLab CI pipelines are not triggered for jobs with very long names.
What is the expected correct behavior?
Pipelines should be triggered regardless of the size of the job name, or GitLab should warn the user if the job name is too long.
Proposal
Update the documentation and the linter to let users know that job names can't be longer than 255 characters
Edited by Sunjung Park