Skip to content

Move pipelines page to GraphQL - Part 6

What does this MR do and why?

Part one: !206072 (merged)

Part two: !207467 (merged)

Part three: !208865 (merged)

Part four: !209348 (merged)

Part five: !210021 (merged)

Part six: YOU ARE HERE 😄

In this MR we emit up the table actions to be captured in the top-level component.

References

Screenshots or screen recordings

Screenshot_2025-10-21_at_4.18.10_p.m.

How to set up and validate locally

  • First visit Build > Pipelines and ensure existing feature works as expected.
  • Next enable Feature.enable(:pipelines_page_graphql) feature flag
  • Visit Build > Pipelines again
  • Play with the retry, cancel, and download artifact buttons
  • It's okay that the rest is missing and broken (filtered search, tabs etc), this is all behind a feature flag

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Payton Burdette

Merge request reports

Loading