1 Commits

Author SHA1 Message Date
pm f2b50a9361 Update .gitea/workflows/deploy.yml
DevSecOps Enterprise Pipeline / security-gate-and-deploy (pull_request) Failing after 15s
2026-06-10 19:09:06 +00:00
2 changed files with 49 additions and 57 deletions
+49 -56
View File
@@ -1,10 +1,11 @@
name: "DevSecOps Enterprise Pipeline"
# ALTERADO: Agora a pipeline reage a QUALQUER alteração em QUALQUER branch,
# permitindo a automação total sem intervenção manual.
# ==========================================
# PONTO 4: TRIGGERS (Push vs PR)
# ==========================================
on:
push:
branches: ["*"] # Escuta todas as branches
branches: [ main ]
pull_request:
branches: [ main ]
@@ -12,54 +13,37 @@ jobs:
security-gate-and-deploy:
runs-on: ubuntu-latest
steps:
- name: 0. Checkout Code
- name: Checkout Code
uses: actions/checkout@v3
with:
fetch-depth: 0
# ==========================================
# ETAPA 1: VALIDACAO FUNCIONAL (TESTES UNITÁRIOS)
# Correm SEMPRE, em qualquer branch.
# ==========================================
- name: 1.1. Setup Node.js Environment
uses: actions/setup-node@v3
with:
node-version: '18'
- name: 1.2. Run Unit Tests (Jest)
run: |
echo ">>> A instalar dependências e a correr testes funcionais..."
# Ajusta para a pasta onde tens o teu package.json (ex: cd backend && npm install)
npm install
npm test
- name: 1.3. Build Application Image
run: docker build -f backend/Dockerfile -t apex-solutions:latest .
# ==========================================
# ETAPA 2: ANÁLISE ESTÁTICA RÁPIDA (SAST, SCA)
# Correm SEMPRE, a cada commit de qualquer branch secundária.
# STAGE 1: STATIC SECURITY TESTING (SAST, SCA)
# ==========================================
- name: 2.1. Secret Scanning (Gitleaks)
- name: Gitleaks Scan
run: |
curl -sL https://github.com/gitleaks/gitleaks/releases/download/v8.18.2/gitleaks_8.18.2_linux_x64.tar.gz | tar -xz -C /tmp
/tmp/gitleaks detect --source . --verbose --redact --log-opts="-1" --exit-code 1
- name: 2.2. Software Composition Analysis (Trivy)
# PONTO 3: Artefactos do Trivy adicionados
- name: Scan Docker Image Vulnerabilities (Trivy)
run: |
curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sh -s -- -b /usr/local/bin
trivy image --severity HIGH,CRITICAL --format table --output trivy-report.txt apex-solutions:latest
trivy image --severity HIGH,CRITICAL --exit-code 1 apex-solutions:latest
# 1. Guarda o output para um ficheiro de texto para o Artefato
trivy image --severity HIGH,CRITICAL --format table --output trivy-report.txt nginx:alpine
# 2. Corre novamente no terminal para forçar a quebra da pipeline se encontrar falhas (Exit-Code 1)
trivy image --severity HIGH,CRITICAL --exit-code 1 nginx:alpine
- name: 2.3. Archive Trivy Report
- name: Archive Trivy Report
if: always()
uses: actions/upload-artifact@v3
with:
name: trivy-sca-report
path: trivy-report.txt
- name: 2.4. Static Application Security Testing (SonarQube)
- name: SonarQube Analysis
run: |
curl -sL https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-5.0.1.3006-linux.zip -o sonar-scanner.zip
unzip -q sonar-scanner.zip
@@ -71,19 +55,17 @@ jobs:
-Dsonar.qualitygate.wait=true
# ==========================================
# ETAPA 3: ANÁLISE DINÂMICA (DAST - OWASP ZAP)
# CRÍTICO: O condicional 'if' garante que este bloco SÓ corre na branch 'main'
# STAGE 2 & 3: DYNAMIC TESTING (ZAP)
# ==========================================
- name: 3.1. Provision Ephemeral Sandbox
if: github.ref == 'refs/heads/main'
- name: Provision Ephemeral Sandbox
run: |
docker rm -f website-test-sandbox || true
docker run -d --name website-test-sandbox apex-solutions:latest
docker run -d --name website-test-sandbox nginx:alpine
docker cp index.html website-test-sandbox:/usr/share/nginx/html/index.html
sleep 5
- name: 3.2. OWASP ZAP Baseline Scan
if: github.ref == 'refs/heads/main'
- name: OWASP ZAP Baseline Scan
run: |
mkdir -p qatests
docker rm -f zap-scanner || true
@@ -94,7 +76,7 @@ jobs:
--link website-test-sandbox:website-test-sandbox \
-v zap-reports:/zap/wrk/:rw \
-t ghcr.io/zaproxy/zaproxy:stable zap-baseline.py \
-t http://website-test-sandbox:3000 \
-t http://website-test-sandbox \
-r report.html \
-I
@@ -102,17 +84,18 @@ jobs:
docker rm -f zap-scanner || true
docker volume rm zap-reports || true
- name: 3.3. Teardown Ephemeral Sandbox
if: always() && github.ref == 'refs/heads/main'
- name: Teardown Ephemeral Sandbox
if: always()
run: |
docker rm -f website-test-sandbox || true
# ==========================================
# ETAPA 4: DEPLOY SEGURO VIA SSH
# CRÍTICO: Só executa se passar em TUDO e for um push final na branch 'main'
# STAGE 4: PRODUCTION DEPLOYMENT (SSH)
# ==========================================
- name: 4.1. Hardened Production Deployment via SSH
# PONTO 6: Deploy Seguro Condicional
# Só executa se for um Push (não PR) e se for na branch main
- name: Hardened Production Deployment via SSH
if: github.ref == 'refs/heads/main' && github.event_name == 'push'
uses: appleboy/ssh-action@v1.0.0
with:
@@ -120,28 +103,38 @@ jobs:
username: ${{ secrets.SSH_USER }}
key: ${{ secrets.SSH_PRIVATE_KEY }}
script: |
echo ">>> A iniciar o Deploy Remoto em Produção via SSH..."
echo ">>> A iniciar Deploy Seguro no Servidor de Produção..."
# 1. Navegar para a pasta do projeto (Ajusta o caminho para o teu servidor real)
cd /opt/website-test
# 2. Puxar as últimas alterações do repositório
git pull origin main
# Tratamento do .env em produção usando os Secrets do Gitea
echo "PORT=3000" > .env
# 3. Tratamento do ficheiro .ENV dinâmico (Frente 2)
# Isto injeta os Secrets do Gitea num ficheiro .env temporário no servidor
echo "PORT=80" > .env
echo "API_SECRET=${{ secrets.API_SECRET_PROD }}" >> .env
# Reconstrói a imagem e reinicia o serviço refletindo o espelho da main
docker build -f backend/Dockerfile -t apex-solutions:production .
docker stop portal-corporativo || true
docker rm portal-corporativo || true
docker run -d -p 3000:3000 --env-file .env --name portal-corporativo apex-solutions:production
echo ">>> Deploy em Produção finalizado com sucesso!"
# 4. Construir e iniciar o contentor de Produção
docker build -t website-test-backend:latest .
docker rm -f website-test-backend || true
docker run -d -p 80:80 --env-file .env --name website-test-backend website-test-backend:latest
echo ">>> Deploy em Produção concluído com sucesso!"
# ==========================================
# ETAPA 5: GESTÃO DE ARTEFACTOS
# STAGE 5: ARTIFACT MANAGEMENT & REPORTING
# ==========================================
- name: Archive ZAP Report (Raw HTML)
if: always() && github.ref == 'refs/heads/main'
if: always()
uses: actions/upload-artifact@v3
with:
name: owasp-zap-report
path: qatests/report.html
path: qatests/report.html
- name: Pipeline Status Notification
if: always()
run: |
echo "Pipeline finished with status: ${{ job.status }}"
-1
View File
@@ -1 +0,0 @@
> Teste de fluxo 100% automatizado: Branch criada a partir da main atualizada.