Change Coverage Fuzzing artifact download to use GraphQL endpoint instead of legacy API for Pipelines Page Part 2
This issue covers using the component from #328194 (closed) once the graphQL query has been created in #328482 (closed)
Order Of Issues
First two issues can be done in parallel.
Order | Issue | Description |
---|---|---|
1 | #328194 (closed) | Adds support to generic download component to take a pipeline id |
1 | #328482 (closed) | Backend issue to implement support for query |
2 | #328481 (closed) | Use component from Part 1. We can stage this in parallel but need to land after backend is complete. |
Proposal
Allow for something like
{
project(fullPath: "project-full-path") {
headPipeline(iid: "the-pipeline-iid") {
jobs(reportTypes: [FUZZING, SAST]) {
nodes {
artifacts(types: [ARCHIVE]) {
nodes {
downloadPath
}
}
}
}
}
}
}
}
The original query used merge request as seen in #251015 (closed)
Frontend Implementation Plan
- Swap out ee/app/assets/javascripts/security_dashboard/components/security_dashboard_vuex.vue usage of
fuzzing-artifact-component
forpipeline-artifacts-download
using the work done in #328194 (closed) - Update unit tests
Edited by -