action #120276
Updated by mkittler over 1 year ago
## Observation > Hello QE, > > first I want to express my gratitude to Chenzi Cao for huge contribution to Bugzilla UAT testing. All reported bugs were fixed, however there are still four issues to be resolved which block deployment to production. Currently the go live is planned for 6.12.-8.12.2022, but there might be further delay. > > One of the big changes is, that XML-RPC support will be dropped and replaced by REST api described here https://bugzilla.readthedocs.io/en/5.0.4/api/ . This enables implementation of several QE metrics identified in the past here: https://confluence.suse.com/display/qasle/QA+Metrics > > If there is someone, who would be interested in working on ingesting the data form Bugzilla, processing it according to identified metrics and storing in InfluxDB InfludDB in order to display it in Grafana, please let me know. It could be an interesting and fun project which would make lives of many people easier. > > Have a nice day > > Jan `openqa_bugfetcher` is currently using XML-RPC (actually JSON-RPC) to fetch bug information. There is a fallback to fetch at least basic information via HTML scraping but that only works for public bugs and might break as well for when there is a major update applied. https://github.com/os-autoinst/openqa_bugfetcher https://github.com/os-autoinst/openqa_bugfetcher/blob/master/openqa_bugfetcher/issues/bugzilla_issue.py After updating the sources, make sure to update the RPM at https://build.opensuse.org/package/show/devel:openQA/openqa_bugfetcher and install the update on the `openqa-service` VM. ## Suggestions - https://bugzilla.readthedocs.io/en/5.0.4/integrating/apis.html#json-rpc - Clarify if XML-RPC is the same as JSON-RPC and thus we need to change our uses - Investigate how to use the REST API for analoguous purposes