ci-test-job-conventionslisted
Install: claude install-skill testland/qa
# ci-test-job-conventions
## Overview
Per-CI platform skills (GitHub Actions / GitLab CI / Jenkins /
CircleCI) cover **how to express** workflows. This skill covers
**what to express** - the cross-platform conventions that apply
regardless of CI tool.
## When to use
- Designing the CI test workflow for a new repo or service.
- Auditing an existing CI config for anti-patterns - retries that
mask flake, no concurrency-cancel, artifacts retained forever.
- PR review of a workflow / `.gitlab-ci.yml` / `Jenkinsfile` change.
- Standardizing test-job conventions across teams on different CI tools.
## How to use this reference
1. **Size the suite, pick the shard count** from the sharding matrix
(§1) and set the per-job timeout for each job type (§8).
2. **Set the retry policy** - which failure classes are safe to retry
vs. quarantine as flake (§2, §3).
3. **Add concurrency-cancel** so a new push cancels the superseded run (§6).
4. **Tier the per-trigger cadence** - what runs per-PR vs per-merge vs
nightly vs pre-release (§5).
5. **Emit JUnit XML and set artifact retention** - the reporting and
cache lookup tables live in
[references/junit-and-cache-lookups.md](references/junit-and-cache-lookups.md);
retention bands in §4.
6. **Guard secrets** with the CI secret store, never in-repo (§7).
Then re-check the workflow against the conventions below.
## §1 - When to shard
Sharding splits a test suite across N parallel jobs. Decision
matrix:
| Suite total runti