Failure modes for multi-project pipelines are difficult to diagnose
Failure modes of the special CI trigger keyword:
trigger:
are difficult to diagnose.
If the job token lacks the permission to trigger, the job is marked as failed. For this type of failure there are a couple issues:
- Because it is a
trigger:
job you cannot click on it, and there is no information about why it failed - It shows up as a failure despite
allow_failure: true
https://ops.gitlab.net/gitlab-com/gl-infra/deployer/blob/265430ec5de45cb242d6cb34a4f1e5b531c75219/.gitlab-ci.yml#L522-530
gstg-gitlab-qa-full:
<<: *only-gstg
stage: gstg-qa
allow_failure: true
variables:
FULL_ONLY: 'true'
<<: *variables-gstg
trigger:
project: gitlab-org/quality/staging
Proposal
- Can we display an error somewhere? Maybe as a tooltip?
- Should these types of failures respect
allow_failure: true
?
Edited by John Jarvis