WIP: Unify behaviors of DAG and Stages when needing a manual job
requested to merge 31264-based-213080-fix-dag-manual-needs into 213080-fix-skipped-needs-with-dependency-tree-approach
What does this MR do?
Related to: #31264 (closed)
This MR is based on the branch of !34450 (closed) 213080-fix-skipped-needs-with-dependency-tree-approach.
The idea is very similar to that one. It is just about unifying behaviors of DAG vs STAGE.
There are failing tests. Also, legacy processing has not been considered in this MR yet.
These changes will be behind a feature flag ci_dag_behaves_same_as_stage.
It can be a breaking change. Please see the examples in the MR diff.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
-
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Furkan Ayhan