potentially unexpected consequences of this change

@manuelgrabowski I have this kind of thing in a pipeline:

my-job:
  [...]
  parallel:
    matrix:
      - PROJECT_URL: https://salsa.debian.org/debian/grep
        SALSA_CI_DISABLE_WRAP_AND_SORT: 0
        SALSA_CI_WRAP_AND_SORT_ARGS: '--wrap-always --short-indent --trailing-comma'
        SALSA_CI_PIUPARTS_ARGS: --extra-repo="deb http://deb.debian.org/debian sid non-free"
        SALSA_CI_BLHC_ARGS: --ignore-line "some harmless line"
        SALSA_CI_SBUILD_VERBOSE: 1
        SALSA_CI_LINTIAN_SUPPRESS_TAGS: 'unreleased-changes'
        SALSA_CI_EXTRA_REPOSITORY: "deb-src http://deb.debian.org/debian unstable main"
        SALSA_CI_EXTRA_REPOSITORY_KEY: /usr/share/keyrings/debian-archive-keyring.gpg
        SALSA_CI_ENABLE_CROSSBUILD_ARM64: 1
  [...]
  rules:
    - if: $CI_SERVER_URL != "https://salsa.debian.org"
      when: never

So this job was not silently failing, it was disabled, and all was good.

Suddenly with the hard limit of 255 characters, the pipeline couldn't run at all.

Given it's a part of the pipeline that was disabled, no problem for me, I just commented out. However Debian runs this pipeline on a self-hosted GitLab instance, so when this 255 limit reach them, and if it's not configurable, they will have to adjust. Check it out at: https://salsa.debian.org/salsa-ci-team/pipeline/-/blob/master/.gitlab-ci.yml?ref_type=heads#L177

Hope that helps to give some context.

Arnaud Rebillout (233d52ea) at 17 Mar 07:57

Arnaud Rebillout (a1bfda6d) at 17 Mar 07:53

Arnaud Rebillout (edde2da5) at 17 Mar 07:48

... and 401 more commits

Arnaud Rebillout (4b2e690d) at 17 Mar 05:28

Arnaud Rebillout (c66f62a7) at 17 Mar 01:37

Arnaud Rebillout (de95056c) at 12 Mar 10:05