Proposal: Overhaul PulpUI Github Actions to a hardened, per job-concern model.

Abierto
  • ¿Algo no está bien?
#362 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
eslint, github-actions, typescript
Área
build-system, ci-cd, security

Línea de trabajo

Start by reviewing the existing workflows under .github/workflows, especially pr.yml, main.yml, schedule.yml, and release.yml, then compare them with the secure-use and OWASP references. The work is done when the workflows follow the proposed per-concern structure, include the listed linting, analysis, scanning, dependency, and release checks, and document their roles.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

The current Continuous Integration (CI) implementation against main runs a set of checks against every pull request, but lacks the newer security posture needed in areas such as static analysis, dependency review and pipeline documentation. As development on pulp-ui accelerates and new features sets land, the pipeline needs to grow to match both to cover new security requirements and provide clear, consistent gateway for code to pass through.

This proposes a full restructure, not an incremental patch, to a job-per-concern reusable-workflow model. Every addition will be mapped explicitly to either OWASP or an existing internal Pulp governance.

High Level Design

Image

Implementations

Continuous checks - pr.yml / main.yml / schedule.yml
  • linting: Handles all linting using application tooling via eslint, prettier and tsc.
  • workflow-lint: Lints the CI workflows and raises issues.
  • tests: Existing test command, unchanged.
  • build: Existing build command, unchanged.
  • sast-quality: Conducts static analysis across the application code using codeql.
  • secrets-scaning: Uses gitleaks as per Pulp governance.
  • dependency-review: Checks newly added packages against current.
  • sca: Conducts full scan of dependency tree.
Release-gated checks - release.yml
  • build: Existing build command, unchanged.build: Existing build command, unchanged.
  • provenance: Generates SBOM then using ephemeral keys, attests against the build.

Out of Scope

  1. Logging and Visibility - requires administrative permissions to conduct an audit on current logging and retention on GitHub actions within this repository to suggest a course of action (COA).

  2. Changes to branching strategy - future branching iterations for feature release will be out of scope.

References

  1. https://docs.github.com/en/actions/reference/security/secure-use
  2. https://owasp.github.io/www-project-top-10-ci-cd-security-risks/
  3. https://github.com/Redtigercod4/pulp-ui/tree/next/.github/workflows
Lenguaje dominante
TypeScript
Estrellas
30
Forks
24
Merge medio
3 d 2 h
PR fusionados (30 d)
20

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de pulp/pulp-ui

Todos los issues de pulp/pulp-ui

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.