taskotron / resultsdb_conventions

#6 Migrate resultsdb_conventions to forgejo (with CI)
Opened by adamwill. Modified

Open
Close Issue

This repository should be migrated to forgejo as part of migrating all Fedora Quality repositories (this isn't in the fedora-qa space any more, but I maintain it, so I'm treating it as part of the group. Not sure what the rest of the taskotron group will do.)

This repository DOES have CI, which makes the migration more complex. A CI strategy will need to be included.

There's a migration checklist and a lot of useful advice in https://pagure.io/fedora-qa/issue/836 , please read that first and follow the steps.

We should decouple it from the taskotron namespace in the new location, and put it into Quality (or whatever the new org is) namespace.

it was previously moved from fedora-qa to taskotron :D I think because it was close to resultsdb. resultsdb is still an active project AFAIK. so it might depend on where resultsdb ends up. I'm not sure who's technically maintaining it atm?

Resultsdb is on github:
https://github.com/release-engineering/resultsdb

(funny that they still have libtaskotron instructions in readme)

Lukas Holecek seems to be maintaining it. Not sure if they are interested in resultsdb_conventions (I don't even know when and if this project is used somewhere).

fedora_openqa uses it for reporting to resultsdb. But I think I did actually get an external user, too - IIRC it was CoreOS (they use it to report results from their CI system into resultsdb, so they show up in Bodhi). I don't know where the code lives, though, @dustymabe might.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/quality/resultsdb_conventions/issues/6

Please continue any further discussion there.
Metadata
None
None
None
Lowest
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.