compose-tracker

Source code that parses pungi logs and opens issues against https://forge.fedoraproject.org/releng/compose-tracker-tickets

Deploying in Fedora

The files for deploying to Fedora's OpenShift Instance are:

• playbooks/openshift-apps/compose-tracker.yml
• roles/openshift-apps/compose-tracker/templates/buildconfig.yml
• roles/openshift-apps/compose-tracker/templates/deploymentconfig.yml
• roles/openshift-apps/compose-tracker/templates/imagestream.yml
• roles/openshift-apps/compose-tracker/templates/secret.yml

The steps for deploying are documented in Fedora Infrastructure SOP document.

This mostly boils down to:

[localhost]$ ssh batcave01.phx2.fedoraproject.org
[batcave01]$ sudo rbac-playbook openshift-apps/compose-tracker.yml

Rough notes for deployment to another OpenShift instance:

Create a new project and build the container.

oc new-project compose-tracker
oc new-build --strategy=docker https://forge.fedoraproject.org/releng/compose-tracker --to compose-tracker-img

Export pagure token to use as an env var and then use kedge to get up and running in openshift:

export FORGEJO_TOKEN=<pagure_token>
kedge apply -f kedge.yaml

Development Environment

The easiest way to run compose_tracker's tests on your local machine is to use tox: just ensure it's installed, and run tox. Alternatively, you can manually set up a virtual environment:

$ python3 -m venv .venv
$ source .venv/bin/activate
(.venv) $

Then you can install the dependencies using the requirements.txt file

(.venv) $ pip install -r requirements.txt -r requirements-test.txt

Finally you can run the tests

(.venv) $ py.test test_consumer.py -v