Backend: Investigate adding dependencies to rules on jobs (in needs)
Release notes
Problem to solve
While working on #31581 (closed) I have realised that we planned to add dependencies to the needs which seemed like a different consideration to job running out of order (the core concept of needs).
In order to deliver rules needs MVP, the below options were descoped.
- https://docs.gitlab.com/ee/ci/yaml/#needsproject -> adding dependencies to download artifacts.
- https://docs.gitlab.com/ee/ci/yaml/#needspipeline -> provides mirroring pipeline status from an upstream pipeline to a bridge
- https://docs.gitlab.com/ee/ci/yaml/#needspipelinejob -> also downloading artifacts from a job in its parent pipeline or another child pipeline
A refactor of some of the existing pipeline dependencies was also raised before we can proceed with adding this option to rules needs.
Intended users
Feature Usage Metrics
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.