mirror of
https://github.com/azaion/gps-denied-onboard.git
synced 2026-06-23 05:21:13 +00:00
Oleksandr Bezdieniezhnykh
1f634c2604
ci/woodpecker/push/02-build-push Pipeline failed
- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests. - Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps. - Updated architectural documentation to include the new demo replay operator flow and its dependencies. - Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation. - Added new entries in the dependencies table for upcoming tasks related to the demo replay flow. These changes improve clarity and usability for operators and developers working with the demo replay system.
2.1 KiB
2.1 KiB
Step 3: CI/CD Pipeline
Role: DevOps engineer Goal: Define the CI/CD pipeline with quality gates, security scanning, and multi-environment deployment. Constraints: Pipeline definition only — produce YAML specification, not implementation.
Steps
- Read
architecture.mdfor tech stack and deployment targets - Read
restrictions.mdfor CI/CD constraints (cloud provider, registry, etc.) - Research CI/CD best practices for the project's platform (GitHub Actions / Azure Pipelines)
- Define pipeline stages:
| Stage | Trigger | Steps | Quality Gate |
|---|---|---|---|
| Lint | Every push | Run linters per language (black, rustfmt, prettier, dotnet format) | Zero errors |
| Test | Every push | Unit tests, blackbox tests, coverage report | 75%+ coverage (see .cursor/rules/cursor-meta.mdc Quality Thresholds) |
| Security | Every push | Dependency audit, SAST scan (Semgrep/SonarQube), image scan (Trivy) | Zero critical/high CVEs |
| Build | PR merge to dev | Build Docker images, tag with git SHA | Build succeeds |
| Push | After build | Push to container registry | Push succeeds |
| Deploy Staging | After push | Deploy to staging environment | Health checks pass |
| Smoke Tests | After staging deploy | Run critical path tests against staging | All pass |
| Deploy Production | Manual approval | Deploy to production | Health checks pass |
- Define caching strategy: dependency caches, Docker layer caches, build artifact caches
- Define parallelization: which stages can run concurrently
- Define notifications: build failures, deployment status, security alerts
Self-verification
- All pipeline stages defined with triggers and gates
- Coverage threshold enforced (75%+)
- Security scanning included (dependencies + images + SAST)
- Caching configured for dependencies and Docker layers
- Multi-environment deployment (staging → production)
- Rollback procedure referenced
- Notifications configured
Save action
Write ci_cd_pipeline.md using templates/ci_cd_pipeline.md.