Source code that parses pungi logs and opens issues against https://pagure.io/releng/failed-composes
  • Python 96.5%
  • Dockerfile 3.5%
Find a file
Clement Verna c4afeddb17
All checks were successful
CI / Run tests (pull_request) Successful in 24s
feat: improve kiwibuild maintainer handling
2026-07-11 20:17:49 +00:00
.forgejo/workflows feat: add CI workflow 2026-07-11 20:12:01 +00:00
.gitignore Add __pycache__ and .pytest_cache to .gitignore 2026-07-11 09:33:56 +00:00
compose-tracker.toml feat: improve kiwibuild maintainer handling 2026-07-11 20:17:49 +00:00
compose_tracker.py feat: improve kiwibuild maintainer handling 2026-07-11 20:17:49 +00:00
Dockerfile fix: update Dockerfile 2026-04-08 22:07:40 +02:00
kedge.yaml fix(compose-tracker, failed-composes): pagure -> forgejo migration 2026-02-09 10:15:55 +01:00
LICENSE Add licensing information 2019-06-03 14:54:24 -04:00
README.md fix(compose-tracker, failed-composes): pagure -> forgejo migration 2026-02-09 10:15:55 +01:00
requirements-test.txt fix: align tests with migrated codebase 2026-07-11 20:17:36 +00:00
requirements.txt Add a tox config to make running tests more convenient 2023-04-22 12:03:20 -07:00
test_consumer.py feat: improve kiwibuild maintainer handling 2026-07-11 20:17:49 +00: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://forge.fedoraproject.org/releng/compose-tracker-issues

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://forge.fedoraproject.org/releng/compose-tracker --to compose-tracker-img

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

export FORGEJO_TOKEN=<forgejo_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