Inspect Docker images and repositories on registries
1baca4ad83
The Gating spec[1] used to recommend having one type of YAML stanza for master, one for released branches. We just discovered today that this breaks when master forks into a release branch: the string 'stable' needs to be manually changed to 'testing', and nobody is going to remember to do that, and I can't think of a (non-tedious) way to add automated checks. As of 2019-08 (09d7d4f), though, the Gating spec suggests having *both* stanzas together in the same gating.yaml file. @pingou himself concurs[2]. Although this is horrible duplication -- two hundred characters, repeated with only six of those different -- it seems cleaner than the maintenance burden of having to update release branches. [1] https://docs.fedoraproject.org/en-US/ci/gating/ [2] https://src.fedoraproject.org/rpms/podman/pull-request/33 Oh, also, add a new 'subject_type' line apparently "required" even though things seem to have been working fine without it. (Source: same commit, 09d7d4f, on gating.adoc). Signed-off-by: Ed Santiago <santiago@redhat.com> |
||
|---|---|---|
| tests | ||
| .gitignore | ||
| containers-auth.json.5.md | ||
| containers-certs.d.5.md | ||
| containers-mounts.conf.5.md | ||
| containers-policy.json.5.md | ||
| containers-registries.conf.5.md | ||
| containers-registries.conf.d.5.md | ||
| containers-registries.d.5.md | ||
| containers-signature.5.md | ||
| containers-storage.conf.5.md | ||
| containers-transports.5.md | ||
| containers.conf | ||
| containers.conf.5.md | ||
| gating.yaml | ||
| mounts.conf | ||
| registries.conf | ||
| seccomp.json | ||
| skopeo.spec | ||
| sources | ||
| storage.conf | ||