release-engineering/resultsdb-updater

A microservice that listens for test results on the message bus and updates ResultsDB

ResultsDB-Updater

ResultsDB-Updater is a micro-service that listens for test results on the CI message bus and updates ResultsDB in a standard format.

Installation

Install the Python dependencies:

pip install -r requirements.txt

Edit the configuration file at:

fedmsg.d/config.py

Generate the entry points for fedmsg-hub:

python setup.py egg_info

Run the service:

fedmsg-hub

Running the service in a container

To build a container image with ResultsDB-Updater run:

$ podman build --tag <IMAGE_TAG> .

IMAGE_TAG is the tag to be applied on the image built.

There are two volumes expected to be mounted when ResultsDB-Updater containers are started:

1. A volume mounted at /etc/fedmsg.d with any *.py file holding fedmsg and ResultsDB-Updater configuration. For an example see fedmsg.d/config.py or the documentation on how to configure fedmsg.

2. A volume mounted at /etc/resultsdb holding the client certificate and private key files, to be used with STOMP when authenticating with the message broker (if configured).

openshift/resultsdb-updater-test-template.yaml defines a template to help deploying ResultsDB-Updater to OpenShift and connecting it to a ResultsDB service, and a message broker (using STOMP).

For the full list of template parameters see:

$ oc process -f openshift/resultsdb-updater-test-template.yaml --parameters

For creating the environment run:

$ oc process -f openshift/resultsdb-updater-test-template.yaml \
             -p TEST_ID=<TEST_ID> \
             -p RESULTSDB_UPDATER_IMAGE=<RESULTSDB_UPDATER_IMAGE> \
             -p RESULTSDB_API_URL=<RESULTSDB_API_URL> \
             -p STOMP_URI=<STOMP_URI> | oc apply -f -

Use the -p option of oc process to override default values of the template parameters.