C1 baseline pipeline#5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Objetivo
Implementa a Etapa 5 do TCC: C1 — Pipeline Baseline.
Este cenário representa a linha de base experimental do pipeline CI/CD, sem ferramentas de segurança como SonarQube, Trivy ou OWASP ZAP.
O objetivo é medir o tempo de execução do pipeline em seu estado mínimo funcional, servindo como referência para comparação com os próximos cenários DevSecOps.
O que foi feito
C1 - Baseline Pipeline./health.GITHUB_STEP_SUMMARY.ci/scripts/measure_step.sh.analysis/raw/c1_baseline.csv.docs/05-c1-baseline-pipeline.md.Arquivos principais
.github/workflows/c1-baseline.ymlci/scripts/measure_step.shanalysis/raw/c1_baseline.csvdocs/05-c1-baseline-pipeline.md.gitattributesObservação experimental
As 5 execuções oficiais do cenário C1 foram coletadas antes da atualização de manutenção das versões das GitHub Actions.
Após a coleta oficial, o workflow foi atualizado para remover o aviso de depreciação relacionado ao runtime Node.js 20. Essa atualização não alterou a lógica experimental do pipeline.