Initial support for ExecDB
ClosedPublic

Authored by jskladan on Feb 23 2015, 8:44 AM.

Details

Summary

Added execdb_url to the config file and changed the ResultsDB calls, so
the uuid gets stored with the job.

Note, that this patch pre-requires updated versions of ResultsDB and
resultsdb_api.

Test Plan

unittests pass; Tested with the whole taskotron-local stuff, and is currently running at taskotron-demo

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 Initial support for ExecDB.Feb 23 2015, 8:44 AM
jskladan updated this object.
jskladan edited the test plan for this revision. (Show Details)
jskladan added reviewers: tflink, kparal, mkrizek.
kparal added inline comments.Feb 23 2015, 10:02 AM
conf/taskotron.yaml.example
62

Let's be a bit more maintainer friendly and add a few words describing it:

## URL of ExecDB server API interface, which tracks task execution status
63

Just a few lines above we have resultsdb_server key. Could we keep the naming consistent and call this execdb_server? (I know, we have some other keys which have _url in their name).

libtaskotron/directives/resultsdb_directive.py
122–130

Can you please update the docstring as well?

jskladan updated this revision to Diff 794.Feb 23 2015, 5:12 PM
  • Changed execdb_url to execdb_server
tflink accepted this revision.Feb 24 2015, 5:10 AM
This revision is now accepted and ready to land.Feb 24 2015, 5:10 AM
kparal accepted this revision.Feb 24 2015, 12:28 PM
Closed by commit rLTRN6d8d0a33c66e: Initial support for ExecDB (authored by Josef Skladanka <jskladan@redhat.com>). · Explain WhyFeb 26 2015, 10:45 AM
This revision was automatically updated to reflect the committed changes.