With the introduction of execdb, we are going to start using a global UUID that follows the execution of a task throughout its lifetime.
Once this UUID exists, existing components will need to be re-factored to support the new UUID. This is a tracking ticket for that rework.
This ticket also depends on https://pagure.io/taskotron/libtaskotron/issue/188
This ticket had assigned some Differential requests: D291 D288 D287 D301 D292
The whole Taskotron stack with the initial support for global UUIDs is running at http://taskotron-demo.cloud.fedoraproject.org/ * Once a job gets spawned by trigger, new job is created in execdb http://taskotron-demo.cloud.fedoraproject.org/execdb from there on, all the pieces have access to the UUID. * ResultsDBs jobs are searchable per-uuid (execdb has a link to the respective job) e.g. http://taskotron-demo.cloud.fedoraproject.org/resultsdb/jobs/d95b2d92-bb3c-11e4-a6d0-fa163e177be9 * the "Taskbot URL" points to the ExecDB job info hub
All of the respective patches are Acked and pushed to Git. Will mark as Resolved once Phab decides to acknowledne the fact
{meme, src=twilight, above=" engage ", below="on the way to the sparkling future"}
bah, forgot about the taskotron-trigger :( Adding as a dependent diff...
{meme, src=twilight, above=" reality ", below="not just unicorns and rainbows :("}
All the respective patches are in Git. Live long and prosper!
Metadata Update from @tflink: - Issue marked as depending on: #50
Login to comment on this ticket.