cicd
/cicd
Obejmuje projekt potoku CI/CD i strategie wdrożeń: kolejność etapów, cache, bramki jakości, blue-green, canary i rollback.
- Autor
- krzysztofsurdy ↗
- Repozytorium
- code-virtuoso ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 23.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 23.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Obejmuje projekt potoku CI/CD i strategie wdrożeń: kolejność etapów, cache, bramki jakości, blue-green, canary i rollback.
Oryginalny opis (EN)
CI/CD pipeline design and deployment strategies: stage ordering, caching, quality gates, blue-green, canary, and rollback. Use to design or improve a delivery pipeline.
Jak działa
- CI vs CD vs CD
- Pipeline design principles
- Deployment strategies overview
- Environment management overview
- Quick reference: pipeline anti-patterns
- Reference Files
- Integration with Other Skills
Podgląd SKILL.md
--- name: cicd description: "CI/CD pipeline design and deployment strategies: stage ordering, caching, quality gates, blue-green, canary, and rollback. Use to design or improve a delivery pipeline." allowed-tools: Read Grep Glob Bash user-invocable: true disable-model-invocation: true --- # CI/CD Pipeline Patterns and Deployment Strategies Continuous Integration, Continuous Delivery, and Continuous Deployment are a spectrum of automation practices. Each builds on the previous one and removes more manual work between a code change and its availability to users. ## CI vs CD vs CD | Practice | What it automates | Gate to next stage | |---|---|---| | **Continuous Integration** | Merging, building, and testing code on every commit | Automated tests must pass before merge | | **Continuous Delivery** | Packaging and promoting artifacts through environments | Manual approval before production deployment | | **Continuous Deployment** | Full path from commit to production without manual steps | Automated quality gates replace human approval | Continuous Integration is the foundation. Without reliable, fast integration, neither delivery nor deployment is sustainable. Start there. --- ## Pipeline design principles A good pipeline gives developers fast, trustworthy feedback and keeps broken code away from users. | Principle | Meaning | |---|---| | **Fast feedback** | Run the cheapest, fastest checks first - lint and unit tests before integration tests and builds | | **Fail early** | Stop the pipeline at the first failure - do not waste time on downstream stages when upstream checks fail | | **Reproducibility** | Every pipeline run with the same inputs must produce the same outputs - pin dependencies, use immutable base images | | **Idempotency** | Re-running a pipeline stage should be safe and produce the same result | | **Isolation** | Each pipeline run operates in a clean environment - no shared state between runs | | **Security by default** | Secrets are injected at runtime, never stored in source - scan for vulnerabilities early | --- ## Deployment strategies overview | Strategy | Downtime | Rollback speed | Infrastructure cost | Complexity | Best for | |---|---|---|---|---|---| | **Blue-Green** | Zero | Instant (traffic switch) | 2x production | Low | Major releases, risk-averse teams | | **Canary** | Zero | Fast (route traffic back) | 1x + small canary slice | Medium | Data-driven teams, high-traffic services | | **Rolling** | Zero (if surge configured) | Slow (reverse rollout) | 1x (reuses existing) | Low | Stateless services, frequent small changes | | **Recreate** | Yes (brief) | Slow (full redeploy) | 1x | Minimal | Dev/staging environments, stateful apps that cannot run two versions | | **Feature Flags** | Zero | Instant (toggle off) | 1x | Medium | Progressive rollout, A/B testing, trunk-based development | No single strategy fits every situation. Many teams combine them, for example canary releases with feature flags to control who sees new functionality. --- ## Environment management overview A typical promotion path moves artifacts through increasingly production-like environments: ``` dev -> staging -> production ``` Principles: - **Artifact immutability** - Build once, deploy the same artifact everywhere. Never rebuild for each environment. - **Configuration separation** - Environment-specific values (database URLs, API keys, feature toggles) live outside the artifact. - **Parity** - Staging should mirror production as closely as possible in infrastructure, data shape, and scale. - **Ephemeral environments** - Spin up isolated environments per pull request for testing and review, then tear them down when the PR closes. --- ## Quick reference: pipeline anti-patterns | Anti-pattern | Problem | Fix | |---|---|---| | Rebuilding artifacts per environment | Different binary in staging vs production | Build once, promote the same artifact | | Long-running monolithic pipeline | Slow feedback, developers context-switch | Parallelize stages, split into focused pipelines | | Secrets in source control | Credential leaks, compliance violations | Use a secrets manager, inject at runtime | | Manual environment setup | Configuration drift, "works on my machine" | Infrastructure as code, containerized builds | | No rollback plan | Extended outages when deployments fail | Automate rollback, test it regularly | | Skipping staging | Production-only bugs discovered too late | Always promote through at least one pre-production environment | --- ## Reference Files | Reference | Contents | |---|---| | [Pipeline Design](references/pipeline-design.md) | Pipeline stages, parallelization, caching, monorepo patterns, secrets management with multi-format examples | | [Deployment Strategies](references/deployment-strategies.md) | Blue-green, canary, rolling deployments, feature flags, zero-downtime migrations, rollback strategies | | [Environment Management](references/environment-management.md) | Environment promotion, infrastructure as code, ephemeral environments, artifact versioning, health checks | --- ## Integration with Other Skills | Situation | Recommended Skill | |---|---| | Monitoring and observability for deployments | `microservices` | | Security scanning in pipelines | `security` | | Testing strategy for CI pipelines | `testing` | | API versioning during deployments | `api-design` |
Pliki w paczce (4)
- SKILL.md 5 KB
- references/deployment-strategies.md 6 KB
- references/environment-management.md 6 KB
- references/pipeline-design.md 5 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · krzysztofsurdy/code-virtuoso | 100 | MIT |
| poppyszn/dev-pops-skills | 100 | MIT |
| chrishuffman5/domain-expert | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki f8b4b69716b4 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95cicd-pipeline
Projektuje potoki CI/CD: lint, testy, budowanie, skan bezpieczeństwa, wdrożenie, cache, równoległość i wycofywanie wdrożeń. - 100deployment-strategies
Opisuje strategie wdrożeń produkcyjnych: blue-green, canary, rolling update i recreate, wraz z zero-downtime, rollbackiem i koordynacją migracji bazy danych. - 100blue-green-deploy
Konfiguruje strategie wdrożeń bez przestojów: blue-green, canary i rolling, z przełączaniem ruchu, kontrolami zdrowia i procedurami wycofania. - 100cicd-pipeline-interviewer
Wciela się w rekrutera inżynierii platformowej i ćwiczy projektowanie pipeline'ów CI/CD: strategie testów i wdrożeń (blue-green, canary, rolling), zarządzanie artefaktami. - 90deployment-strategies
Pomaga bezpiecznie wprowadzać zmianę na produkcję: blue-green, canary, rolling, flagi funkcji i rollback, także przy wdrożeniu bez przestoju. - 100harness-cd
Prowadzi wdrożenia w Harness CD: Kubernetes, Helm, Terraform, ECS i serverless, strategie canary, blue-green i rolling, bramki zatwierdzeń oraz wycofywanie wdrożeń.