Problem to solve

After changing my pipeline to a downstream approach

merge_request_job:
  rules:
    - if: $JOB_ID != null
      when: never
    - when: on_success
  trigger:
    include:
      - local: .gitlab/ci-pipeline.yml
    strategy: depend      
check_api_job:
  rules:
    - if: $JOB_ID == "openapi" || ($CI_PIPELINE_SOURCE == "chat" && $CHAT_INPUT == "/openapi")
  trigger:
    include:
      - local: .gitlab/check-api-pipeline.yml
    strategy: depend

I see always error status for merge_request_job saying "downstream pipeline cannot be created" "the rules configuration" but the downstream job is also being triggered as expected. Both different statuses for the same commit id (as shown on the attached image). My question is, is there anyway to not show that error status because of the rules not being matched and just see the triggered job?

image1314×503 59.6 KB

Steps to reproduce

• add above content to .gitlab-ci.yml file
• create .gitlab/check-api-pipeline.yml and .gitlab/ci-pipeline.yml with whatever the valid pipelines
• push changes to specific branch and to create a MR against default branch

Configuration

merge_request_job:
  rules:
    - if: $JOB_ID != null
      when: never
    - when: on_success
  trigger:
    include:
      - local: .gitlab/ci-pipeline.yml
    strategy: depend      
check_api_job:
  rules:
    - if: $JOB_ID == "openapi" || ($CI_PIPELINE_SOURCE == "chat" && $CHAT_INPUT == "/openapi")
  trigger:
    include:
      - local: .gitlab/check-api-pipeline.yml
    strategy: depend

Versions

Please select whether options apply, and add the version information.

• Self-managed
• GitLab.com SaaS
• Self-hosted Runners

Versions

v16.11.6-ee

any clue on this?