mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
kevinveenbirkenbachandClaude Sonnet 4.6
79ca7137da
- Rename continuous_integration.md to ci.md - Move debugging.md into debugging/ci.md and apply documentation standards - Add debugging/network.md with Docker pull error guidance (MTU, IPv6, connectivity) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
CI Failures and Debugging 🐛
If CI fails, follow a clean debugging workflow:
- Export the raw failing logs.
- Save them locally as
job-logs.txt. - Decide whether the failure belongs to your branch or to something unrelated.
- Fix related failures in the same branch.
- Open an issue for unrelated failures instead of mixing them into your branch.
Important 🚨
- You MUST NOT debug from screenshots alone. Use raw logs.
- You MUST NOT commit log files to the repository.
- If a Playwright job fails, you MUST also download the Playwright assets, store them in
/tmp/, and analyze them together with the logs.
Manual CI Jobs 🎯
You SHOULD use targeted manual CI jobs instead of rerunning the full pipeline if you only need one focused check.
Prefer the manual workflow in entry-manual.yml:
- Select your branch.
- Use
debianunless you have a clear reason to use a different distro. - Limit the run to the affected app when possible.
This gives faster feedback and protects shared CI runners.
More information here.