Currently, FTI status is determined from bugzilla. That's not always up to date. Let's try showing status from https://pagure.io/fedora-health-check/
Metadata Update from @frantisekz: - Issue assigned to frantisekz
This is pending backend work, I'll reassign to @lbrabec once completed.
Preliminary backend work done in: https://pagure.io/fedora-qa/oraculum/pull-request/19
Metadata Update from @frantisekz: - Assignee reset
I need some clarification here. At the time of writing this comment, package python-jep fails to install (according to bugzilla).
python-jep
There is a list of keywords in bug info I receive from back end, for python-jep the list contains string FTI. Based on this string, front end shows FTI badge next to package name:
FTI
Back end now sends back additional info based on fedora-health-check, for python-jep I get:
"python-jep": { "fails_to_install": false, "releases": [] }
What should be the logic here? Ignore kyword FTI in bug info and consider only fedora-health-check?
Finally, back end provides list of releases where the package fails to install (see json snippet above). To show, it I can another row with all the releases in it or new row for every release.
I plan to keep the FTI badge, as it is easily visible.
WDYT @churchyard
Yes.
The bugzilla might or might not be open depending on various circumstances. Show the bugzilla as any other bugzilla. OTOH fedora-health-check should provide current-ish real information for stable and testing.
Similarly, the FTBFS bugzilla might o might not be open, even if koschei reports the build broken.
Metadata Update from @lbrabec: - Issue assigned to lbrabec
Deployed, see our test instance.
Metadata Update from @lbrabec: - Issue status updated to: Closed (was: Open)
Side note: the fedora-health-check data is updated daily at 22:00 (CE(S)T). I'm working on a rewrite of the code as a server that can serve status web sites and data on demand, instead of storing it in git, which could then run and update data continuously. :)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/apps/packager_dashboard/issues/4
Please continue any further discussion there.