Source code that parses pungi logs and opens issues against https://pagure.io/releng/failed-composes
  • Python 96.4%
  • Dockerfile 3.6%
Find a file
Tomas Hrcka 67aff9fbfd Update python lib path to 3.11
Signed-off-by: Tomas Hrcka <thrcka@redhat.com>
2023-05-23 15:27:21 +02:00
.gitignore update .gitignore 2022-06-16 15:04:16 +02:00
compose-tracker.toml Adding compose tracking for ELN composes 2021-11-11 14:40:29 -05:00
compose_tracker.py Current Koji task IDs are now nine digits, not eight 2023-04-22 12:04:58 -07:00
Dockerfile Update python lib path to 3.11 2023-05-23 15:27:21 +02:00
kedge.yaml README: update to dev documentation 2019-06-03 15:50:32 -04:00
LICENSE Add licensing information 2019-06-03 14:54:24 -04:00
README.md Add a tox config to make running tests more convenient 2023-04-22 12:03:20 -07:00
requirements-test.txt Add a tox config to make running tests more convenient 2023-04-22 12:03:20 -07:00
requirements.txt Add a tox config to make running tests more convenient 2023-04-22 12:03:20 -07:00
test_consumer.py Current Koji task IDs are now nine digits, not eight 2023-04-22 12:04:58 -07:00
tox.ini Add a tox config to make running tests more convenient 2023-04-22 12:03:20 -07:00

compose-tracker

Source code that parses pungi logs and opens issues against https://pagure.io/releng/failed-composes

Deploying in Fedora

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

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://pagure.io/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 PAGURE_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