taskotron / libtaskotron

#188 Initial ExecDB Implementation
Closed: Fixed Opened by tflink.

Closed: Fixed
Reopen Issue

While not strictly required for disposable clients from a functionality POV, it will increase our ability to keep track of Taskotron status and act more efficiently as administrators of that system.

There has been a lot of discussion about [[ planning/execdb_features | execdb features ]] but we only need a subset of those features for the initial implementation - enough to give admins a central place to look for information on executed tasks for triage purposes.

This ticket is a duplicate of https://pagure.io/taskotron/issue/50

This ticket also depends on https://pagure.io/taskotron/issue/74

Initial implementation to be found here: https://bitbucket.org/rajcze/execdb/src
The changes required in trigger: https://bitbucket.org/fedoraqa/taskotron-trigger/branch/feature/execdb

Once there is some spare time, @tflink and I should spawn a dev/stg instance of taskotron with these changes applied.

The ExecDB initial implementation is done https://bitbucket.org/rajcze/execdb/ and runs with the whole stack here: http://taskotron-demo.cloud.fedoraproject.org/execdb

Metadata Update from @tflink:
- Issue marked as depending on: #214
Metadata
None
None
None
None
Low
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.