Documentation for 'trigger' key in GitLab CI missing details regarding compatabilities
Problem to solve
The trigger syntax utilized in our GitLab CI is missing details as to where we fall short on compatibility and feature integration. Example, the use of downstream jobs which have an exception allowing only 'triggered' pipelines, actually fails as noted in this issue: #32414 (closed)
Because this is not documented, in that issue we have a few community members that are running into testing and learning certain capabilities are not usable.
It'd be nice if there were a list of what capabilities the trigger key provides and where it falls short to better enable persons whom want to utilize this feature.
Further details
Proposal
There's confusion on how only/except with trigger/pipeline affect different multi-project pipelines.
We should add clarification which pipelines pipelines would trigger only:[triggers] and except:[triggers] jobs and which will trigger only:[pipelines] and except:[pipelines] jobs.
We should also look into adding descriptive examples for this as well as revisiting the descriptions for this in the CI YAML reference documentation.
Who can address the issue
~"group::continuous integration" devopsverify