ci-cd-automation
Skill0 starsChanged 28 days agoMITView on GitHub
Intégration continue, déploiement continu, pipelines CI/CD, et automatisation des workflows DevOps. Use when creating or debugging a CI/CD pipeline, a GitHub Actions workflow, automated build, test or deployment, release automation, or when the user says pipeline, CI/CD, deploiement automatique ou integration continue.
Files
CI/CD Automation
Guide complet pour l'intégration continue, le déploiement continu et l'automatisation DevOps.
Pipeline CI/CD Standard
Code Push → Lint → Test → Build → Security Scan → Deploy Staging → E2E Tests → Deploy ProductionGitHub Actions
Configuration de Base
name: CI/CD Pipeline
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
env:
NODE_VERSION: '20'
REGISTRY: ghcr.io
IMAGE_NAME: ${{ github.repository }}
jobs:
# Phase 1: Qualité du code
quality:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: ${{ env.NODE_VERSION }}
cache: 'npm'
- name: Install dependencies
run: npm ci
- name: Lint
run: npm run lint
- name: Type check
run: npm run typecheck
- name: Format check
run: npm run format:check
# Phase 2: Tests
test:
runs-on: ubuntu-latest
needs: quality
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: ${{ env.NODE_VERSION }}
cache: 'npm'
- name: Install dependencies
run: npm ci
- name: Unit tests
run: npm run test:unit -- --coverage
- name: Integration tests
run: npm run test:integration
env:
DATABASE_URL: postgresql://test:test@localhost:5432/test
- name: Upload coverage
uses: codecov/codecov-action@v4
with:
files: ./coverage/lcov.info
# Phase 3: Build
build:
runs-on: ubuntu-latest
needs: test
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: ${{ env.NODE_VERSION }}
cache: 'npm'
- name: Install dependencies
run: npm ci
- name: Build
run: npm run build
- name: Upload build artifact
uses: actions/upload-artifact@v4
with:
name: build
path: dist/
# Phase 4: Security Scan
security:
runs-on: ubuntu-latest
needs: build
steps:
- uses: actions/checkout@v4
- name: Run Trivy vulnerability scanner
uses: aquasecurity/trivy-action@master
with:
scan-type: 'fs'
scan-ref: '.'
format: 'table'
exit-code: '1'
severity: 'CRITICAL,HIGH'
# Phase 5: Deploy
deploy:
runs-on: ubuntu-latest
needs: security
if: github.ref == 'refs/heads/main'
environment: production
steps:
- uses: actions/checkout@v4
- name: Deploy to production
run: |
echo "Deploying to production..."
# Votre script de déploiement iciWorkflows Utiles
Auto-Label PR
name: Auto Label PR
on:
pull_request:
types: [opened, synchronize]
jobs:
label:
runs-on: ubuntu-latest
steps:
- uses: actions/labeler@v5
with:
configuration-path: .github/labeler.ymlAuto-Assign Reviewers
name: Auto Assign Reviewers
on:
pull_request:
types: [opened]
jobs:
assign:
runs-on: ubuntu-latest
steps:
- uses: kentaro-m/auto-assign-action@v2
with:
assignees: ${{ github.actor }}
reviewers: team-leadsStale Issues
name: Stale Issues
on:
schedule:
- cron: '0 0 * * *'
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v9
with:
stale-issue-message: 'This issue is stale'
stale-pr-message: 'This PR is stale'
days-before-stale: 30
days-before-close: 7Docker
Dockerfile Optimisé
# Stage 1: Build
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build
# Stage 2: Production
FROM node:20-alpine AS production
WORKDIR /app
RUN addgroup -g 1001 -S nodejs && adduser -S nextjs -u 1001
COPY --from=builder --chown=nextjs:nodejs /app/dist ./dist
COPY --from=builder --chown=nextjs:nodejs /app/node_modules ./node_modules
COPY --from=builder --chown=nextjs:nodejs /app/package.json ./package.json
USER nextjs
EXPOSE 3000
CMD ["node", "dist/index.js"]Docker Compose
version: '3.8'
services:
app:
build: .
ports:
- "3000:3000"
environment:
- NODE_ENV=production
- DATABASE_URL=postgresql://postgres:password@db:5432/myapp
depends_on:
db:
condition: service_healthy
restart: unless-stopped
db:
image: postgres:16-alpine
environment:
POSTGRES_DB: myapp
POSTGRES_USER: postgres
POSTGRES_PASSWORD: password
volumes:
- postgres_data:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U postgres"]
interval: 10s
timeout: 5s
retries: 5
redis:
image: redis:7-alpine
ports:
- "6379:6379"
volumes:
- redis_data:/data
volumes:
postgres_data:
redis_data:Deployment Strategies
Blue-Green Deployment
# Déploiement Blue-Green
deploy-blue:
runs-on: ubuntu-latest
steps:
- name: Deploy to blue environment
run: |
# Déployer la nouvelle version sur blue
kubectl set image deployment/app-blue app=myapp:${{ github.sha }}
- name: Run smoke tests
run: |
# Tests sur blue
curl -f https://blue.example.com/health
- name: Switch traffic to blue
run: |
# Basculer le traffic
kubectl patch service/app -p '{"spec":{"selector":{"version":"blue"}}}'Canary Deployment
# Déploiement Canary
deploy-canary:
runs-on: ubuntu-latest
steps:
- name: Deploy canary (10% traffic)
run: |
# Déployer 10% du traffic
kubectl apply -f canary-deployment.yaml
- name: Monitor metrics
run: |
# Surveiller les métriques
sleep 300
# Vérifier les erreursMonitoring & Alerting
Prometheus + Grafana
# docker-compose.monitoring.yml
version: '3.8'
services:
prometheus:
image: prom/prometheus
volumes:
- ./prometheus.yml:/etc/prometheus/prometheus.yml
ports:
- "9090:9090"
grafana:
image: grafana/grafana
environment:
- GF_SECURITY_ADMIN_PASSWORD=admin
ports:
- "3001:3000"
volumes:
- grafana_data:/var/lib/grafana
alertmanager:
image: prom/alertmanager
volumes:
- ./alertmanager.yml:/etc/alertmanager/alertmanager.yml
ports:
- "9093:9093"
volumes:
grafana_data:Checklist CI/CD
- Le pipeline se déclenche-t-il sur chaque PR ?
- Les tests sont-ils exécutés avant le merge ?
- Le code est-il linté et formaté ?
- La sécurité est-elle vérifiée (SAST, dependency scan) ?
- Le build est-il déployé en staging ?
- Les tests E2E sont-ils exécutés ?
- Le déploiement en production est-il automatisé ?
- Les alertes sont-elles configurées ?
- Le rollback est-il possible ?
- Les logs sont-ils centralisés ?
Outils
| Catégorie | Outil | Usage |
| CI/CD | GitHub Actions | Pipeline d'intégration |
| Container | Docker | Conteneurisation |
| Orchestration | Kubernetes | Orchestration containers |
| IaC | Terraform | Infrastructure as Code |
| Monitoring | Prometheus + Grafana | Métriques et dashboards |
| Alerting | PagerDuty / Slack | Notifications |
| Secrets | Vault / AWS Secrets | Gestion des secrets |
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- LuisUrrutia/skills★ 2same name
- nilkanthdesai76/universal-agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository43 other files it gives its agents.
- 3d-performance-accessibilitySkill
- 3d-web-designSkill
- accessibilitySkill
- admin-shellSkill
- anti-hallucinationSkill
- api-designSkill
- architectureSkill
- backoffice-designSkill
- banner-designSkill
- bragSkill
- brag-slimSkill
- brandSkill
- coding-standardsSkill
- context-engineeringSkill
- databaseSkill
- data-tablesSkill
- designSkill
- design-system-shadcnSkill
- design-systemSkill
- documentationSkill
- form-designSkill
- git-workflowSkill
- gsap-coreSkill
- gsap-frameworksSkill
- gsap-performanceSkill
- gsap-pluginsSkill
- gsap-reactSkill
- gsap-scrolltriggerSkill
- gsap-timelineSkill
- gsap-utilsSkill
- monitoring-observabilitySkill
- motion-design-webSkill
- performanceSkill
- saas-design-systemSkill
- saas-system-designSkill
- saas-ui-designSkill
- securitySkill
- slidesSkill
- state-managementSkill
- testingSkill
- threejs-webglSkill
- ui-stylingSkill
- ui-ux-pro-maxSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

