Skip to content

github-actions.md

Latest commit

 

History

History
49 lines (33 loc) · 935 Bytes

github-actions.md

File metadata and controls

49 lines (33 loc) · 935 Bytes

CI and Automation

This document outlines a practical CI layout for this repository.

Suggested Pipeline Stages

  1. Lint and static checks
  2. Collection and playbook validation
  3. Scenario validation

Stage 1: Lint

pre-commit run --all-files

Stage 2: Collection and Playbook Checks

uv run poe test ansible-collection

Stage 3: Scenario Validation

uv run poe test qemu

Optional Build Artifact Stage

For release workflows, produce image artifacts:

uv run poe build
uv run poe status

Caching Tips

  • cache Python dependencies used by uv
  • cache downloaded collection content when suitable
  • avoid caching generated image artifacts unless release jobs require it

Failure Triage Order

  1. Read pre-commit output first.
  2. Check collection validation output.
  3. Check scenario create/converge/verify logs.
  4. Reproduce locally with the same command sequence.