greenwave

#179 Rename greenwave.yaml to criteria.yaml.
Merged by ralph. Opened by ralph.
ralph/greenwave bikeshed  into  master

Download 179.patch

We're going to be asking packagers to put these files in their dist-git repos.
Rather than name the file after the system that expects it, name it after the
usecase with respect to the packagers' workflow. The files defines criteria
for their package to pass various gating points, so call it criteria.yaml.

:bike: :house_with_garden:

I kinda like greenwave.yaml more since it states name of application that processes it (similar to .travis.yml, appveyor.yml, Dockerfile, Doxyfile ...) and it's probably easier to google it out.

But it's not a strong opinion.

Yeah. In all those cases, the user knows the name of the tool and interacts with it by name (they run docker to build, then check travis's web UI, etc..). In our case, the end user (the packager) never has to interact directly with greenwave. It is glue between the test systems and various release/promotion systems.

That reasoning makes sense to me so :+1:

But if you are taking bikesheds on this, I would say that "criteria" sounds a bit too general. Criteria about what, to allow what? Some alternatives for consideration:

test-criteria.yaml
test-gating.yaml
gating.yaml
test-policy.yaml
gating-policy.yaml

Cool. I'm game for either criteria.yaml or gating.yaml.

rebased onto ede4b87f935bf61a758f42e9dfe056049e6ab890

Pull-Request has been merged by ralph
Metadata
None
No Tags
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.