Dynamically generated downstream child pipeline can cancel its parent
Observed behavior
It looks like under some unknown conditions, a dynamically generated pipeline can potentially cancel the parent pipeline which triggered it. This is not desired.
The desired behavior is that both the parent and child pipeline should keep running because there's no other newer pipeline
Example pipeline: https://gitlab.com/gitlab-org/gitlab/-/pipelines/663812939
Current configurations
Both the parent and child pipelines have:
default:
interruptible: true
The child pipeline is dynamically generated via trigger.include.artifact
: https://docs.gitlab.com/ee/ci/pipelines/downstream_pipelines.html#dynamic-child-pipelines