Backport of Validate parallel:matrix expanded job name length
What does this MR do and why?
This MR backports the revert done in !227624 (merged) (Revert "Merge branch '584573-fix-parallel-matrix-job-name-length-validation' into 'master'") from master to 18-10-stable-ee.
The original change ( #584573 ) added validation to reject CI jobs whose expanded parallel:matrix job name exceeded the 255-character limit. That caused incidents in customer pipelines where existing configurations with long matrix-expanded job names started failing.
By backporting the revert into 18.10, we restore the previous behaviour and allow these long, matrix-expanded job names again, unblocking affected customer pipelines while we work on a safer follow-up fix.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
- This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
- The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes).
- The MR title is descriptive (e.g. "Backport of 'title of default branch MR'"). This is important, since the title will be copied to the patch blog post.
- Required labels have been applied to this merge request
- severity label and bug subtype labels (if applicable)
- If this MR fixes a bug that affects customers, the customer label has been applied.
- This MR has been approved by a maintainer (only one approval is required).
- Ensure the
e2e:test-on-omnibus-eejob has succeeded, or if it has failed, investigate the failures. If you determine the failures are unrelated, you may proceed. If you need assistance investigating, reach out to a Software Engineer in Test in #s_developer_experience.
Note to the merge request author and maintainer
If you have questions about the patch release process, please:
- Refer to the patch release runbook for engineers and maintainers for guidance.
- Ask questions on the
#releasesSlack channel (internal only). - Once the backport has been merged, the commit changes will be automatically deployed to a release environment that can be used for manual validation. See after merging runbook for details.