Manually running the pipeline results in failure in the build jobs.

When I try to run the pipeline manually (via "Run Pipeline" button), it fails with this error in the build jobs:

Pulling docker image registry.salsa.debian.org/salsa-ci-team/pipeline/base: ...
WARNING: Failed to pull image with policy "always": invalid reference format (manager.go:250:0s)
ERROR: Job failed: failed to pull image "registry.salsa.debian.org/salsa-ci-team/pipeline/base:" with specified policies [always]: invalid reference format (manager.go:250:0s)

I don't change the default values of the pipeline variables when I run it manually.

But when I run the pipeline by creating a new branch (Which triggers the pipeline to run automatically), it runs successfully.

Example 1: vim package

I didn't add any commit in this fork, just forked it from the vim main repo and created a new branch to trigger the pipeline.

Successful automatic pipeline run: https://salsa.debian.org/ahmedsiam/vim/-/pipelines/656445

Failed manual pipeline run: https://salsa.debian.org/ahmedsiam/vim/-/pipelines/658297

Failed job output in manual run: https://salsa.debian.org/ahmedsiam/vim/-/jobs/5507617

Example 2: hithere package

In this package I use the pipeline through setting the CI/CD configuration file option as recipes/debian.yml@salsa-ci-team/pipeline.

Failed manual pipeline runs in different branches but that has the same commits (all of them fail for the same error):

Successful automatic pipeline runs (via creating a new branch):

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information