<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary - possibly related to https://gitlab.com/gitlab-org/gitlab/-/issues/230933 (or Dup) Today we were not possible to trigger a pipeline due to a first unknown error `No stages / jobs for this pipeline` like in the screenshot - yesterday evening everything worked: . After further investigations we found the issue. The issue is, that when running a pipeline from web via the `Run Pipeline` button, the variable `CI_PIPELINE_SOURCE` does not contain `web`, but `api`. Yesterday everything worked well, so it's highly probable that it's related with the release tonight. ### Steps to reproduce - Create a CI pipeline and just `echo "$CI_PIPELINE_SOURCE"` - Trigger it via the `Run Pipeline` Button ### Temporary workaround Add `api` to the `only` list like: ```yaml only: refs: - api - web ``` ### What is the current *bug* behavior? The `$CI_PIPELINE_SOURCE` is `api` ### What is the expected *correct* behavior? The `$CI_PIPELINE_SOURCE` should be `web` ~bug