Update ResulsDB directive to work with API v2.0
ClosedPublic

Authored by jskladan on Oct 5 2016, 12:29 PM.

Details

Summary

Changes resultsdb directive to use the new api/workflow when creating results.

Once we deploy new ExecDB, I'd like to move the "create_resultsdb_group" to
ExecDB, which would actually create the group, with a meaningfull description,
and resultsdb directive would then only use the uuid to reference it.

Test Plan

unittests updated

Diff Detail

Repository
rLTRN libtaskotron
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
jskladan retitled this revision from to Update ResulsDB directive to work with API v2.0.Oct 5 2016, 12:29 PM
jskladan updated this object.
jskladan edited the test plan for this revision. (Show Details)
jskladan added a reviewer: libtaskotron.
kparal accepted this revision.Oct 6 2016, 1:00 PM
kparal added a reviewer: kparal.
kparal added a subscriber: kparal.
kparal added inline comments.
libtaskotron/directives/resultsdb_directive.py
150

Can you add '/%s' % name to the end, so that it leads e.g. to https://fedoraproject.org/wiki/Taskotron/Tasks/dist.depcheck ? (We'll need to move the existing pages of course). We can then tell people to pester task maintainers to create documentation for their tasks (rpmgrill etc), or even let community create some documentation themselves.

We'll also need to change our current testcases to follow the same scheme.

This revision is now accepted and ready to land.Oct 6 2016, 1:00 PM
mkrizek accepted this revision.Oct 6 2016, 1:21 PM
mkrizek added a reviewer: mkrizek.
tflink accepted this revision.Oct 7 2016, 4:26 AM
tflink added a reviewer: tflink.

With what @kparal said about the url

Closed by commit rLTRNc637443a9b7f: Update ResulsDB directive to work with API v2.0 (authored by Josef Skladanka <jskladan@redhat.com>). · Explain WhyOct 7 2016, 11:18 AM
This revision was automatically updated to reflect the committed changes.