Integrate new pipeline query for pipeline editor
What does this MR do?
For #280829 (closed)
This integrates the new graphql query for fetching the pipeline status by commit sha
. This is used in the pipeline status component of the pipeline editor (located in the pipeline header). The pipeline status will regularly poll for the pipeline details triggered by the latest commit.
Since we're now using the actual query, the client resolver has been removed from the feature and tests.
Once this is merged, we can enable the pipeline_status_for_pipeline_editor
feature flag so it can be used in production. See #321518 (closed) for the rollout of the feature flag.
Local Testing
To test this on gdk, please follow these steps:
- Enable the
pipeline_status_for_pipeline_editor
feature flag. - Go to the pipeline editor. The pipeline status for the latest commit should be displayed.
- Edit the file and commit the changes. The pipeline status component should automatically fetch and display the status of the pipeline triggered by the new commit.
Screenshots
State | Screen |
---|---|
Initial page load showing the pipeline status of the latest commit | ![]() |
After making a new commit in the pipeline editor | ![]() |
Test Recording
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- This is behind a disabled feature flag, so no changelog is required.
- [-] 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