3.6 KiB
3.6 KiB
Pipeline/Run-Centric View
Module
Web
Status
IMPLEMENTED
Description
Runs feature exists in the frontend with first-signal card components and prefetch services, but a full pipeline-centric view as described in the advisory is only partially present.
What's Implemented
- Existing components:
approval-detail(src/Web/StellaOps.Web/src/app/features/release-orchestrator/approvals/approval-detail/approval-detail.component.ts)approval-queue(src/Web/StellaOps.Web/src/app/features/release-orchestrator/approvals/approval-queue/approval-queue.component.ts)promotion-request(src/Web/StellaOps.Web/src/app/features/release-orchestrator/approvals/promotion-request/promotion-request.component.ts)active-deployments(src/Web/StellaOps.Web/src/app/features/release-orchestrator/dashboard/components/active-deployments/active-deployments.component.ts)pending-approvals(src/Web/StellaOps.Web/src/app/features/release-orchestrator/dashboard/components/pending-approvals/pending-approvals.component.ts)pipeline-overview(src/Web/StellaOps.Web/src/app/features/release-orchestrator/dashboard/components/pipeline-overview/pipeline-overview.component.ts)recent-releases(src/Web/StellaOps.Web/src/app/features/release-orchestrator/dashboard/components/recent-releases/recent-releases.component.ts)dashboard(src/Web/StellaOps.Web/src/app/features/release-orchestrator/dashboard/dashboard.component.ts)deployment-list(src/Web/StellaOps.Web/src/app/features/release-orchestrator/deployments/deployment-list/deployment-list.component.ts)deployment-monitor(src/Web/StellaOps.Web/src/app/features/release-orchestrator/deployments/deployment-monitor/deployment-monitor.component.ts)
- Existing routes:
approvals.routes.ts,dashboard.routes.ts,deployments.routes.ts,environments.routes.ts,evidence.routes.ts,releases.routes.ts,workflows.routes.ts
What's Missing
- Pipeline run detail view: No dedicated "run detail" view showing a single pipeline execution with its stages, gates, evidence collection, and outcome
- Run-centric navigation: Components exist for approvals, deployments, and releases but no unified "runs" listing that ties them together as a single pipeline execution
- First-signal card integration: First-signal card components exist in the
runs/feature but may not be integrated into the pipeline-centric view - Backend API wiring: Dashboard components may use stub/mock data pending backend endpoint integration
- Unit/E2E test coverage: Components likely lack comprehensive test coverage
Implementation Plan
- Create a unified "pipeline run" detail view connecting scan, gate evaluation, approval, and deployment stages
- Wire pipeline-overview component to backend API for live pipeline status
- Add run-centric navigation linking approval, deployment, and evidence views
- Add unit and E2E test coverage for pipeline dashboard components
E2E Test Plan
- Setup:
- Log in with a user that has appropriate permissions
- Navigate to
/release-orchestrator - Ensure test data exists (scanned artifacts, SBOM data, or seed data as needed)
- Core verification:
- Verify the component renders correctly with sample data
- Verify interactive elements respond to user input
- Verify data is fetched and displayed from the correct API endpoints
- Edge cases:
- Verify graceful handling when backend API is unavailable (error state)
- Verify responsive layout at different viewport sizes
- Verify accessibility (keyboard navigation, screen reader labels, ARIA attributes)