Track the integration effort of resultsdb and Greenwave and provide input when necessary. This integration affects the CI pipeline at the place where CI results are stored for Fedora/public consumption.
Acceptance Criteria - Greenwave knows where to retrieve CI results information - Greenwave knows the data structure to expect in returns to its queries - Greenwave knows how to interpret these information to make its decisions
Tasks:
[x] Track discussion on ticket: https://pagure.io/greenwave/issue/33 [x] Track progress on the fedmsg client to load data into CI's resultsdb https://pagure.io/ci-resultsdb-listener [x] Fix bug reported on the listener that makes it upload the data in an inproper way [ ] Finish the details around the integration: https://pagure.io/greenwave/issue/61 [ ] Package ci-resultsdb-listener and re-deploy it properly (instead of from a git checkout) [x] Follow up on the tuning of the rules for GW and fix needed in bodhi: https://pagure.io/greenwave/issue/68
Metadata Update from @dperpeet: - Issue assigned to pingou
Follow up on the tuning of the rules for GW and fix needed in bodhi: https://pagure.io/greenwave/issue/68
This has been fixed in : - https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=b2664e2a8f91eba3d29a7ede88779eb78c4a903e and - https://github.com/fedora-infra/bodhi/pull/1769
Metadata Update from @pingou: - Assignee reset
Metadata Update from @pingou: - Issue assigned to pingou
@pingou Could you please update the status of this ticket. What needs to be done?
Log in to comment on this ticket.