Initial support for ExecDB
ClosedPublic

Authored by jskladan on Feb 26 2015, 2:04 PM.

Details

Summary

Create new job in ExecDB, and submit data gathered from the FedMsg.

Test Plan

Tested locally, and currently running at taskotron-demo

Diff Detail

Repository
rTRGR taskotron-trigger
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 26 2015, 2:04 PM
jskladan updated this object.
jskladan edited the test plan for this revision. (Show Details)
jskladan added reviewers: mkrizek, tflink.
tflink requested changes to this revision.Feb 26 2015, 2:15 PM

overall, looks good to me outside of the naming inconsistency we have between trigger and libtaskotron - we just need to be careful with this because a buildmaster config change is needed. that change is in dev, IIRC but not in stg or production

conf/trigger.cfg.example
10

I wonder if we should be keeping these names consistent throughout our code - libtaskotron is execdb_server

This revision now requires changes to proceed.Feb 26 2015, 2:15 PM
mkrizek added inline comments.Feb 26 2015, 2:30 PM
jobtriggers/config.py
16

Why is this changed? It's easier for testing to have StreamTrigger as default (you don't need to install buildbot).

jskladan updated this revision to Diff 819.Feb 26 2015, 3:12 PM
  • Renamed execdb_url to execdb_server
tflink accepted this revision.Feb 26 2015, 3:44 PM
This revision is now accepted and ready to land.Feb 26 2015, 3:44 PM
Closed by commit rTRGR01a9ddd357cc: Initial support for ExecDB (authored by Josef Skladanka <jskladan@redhat.com>). · Explain WhyFeb 26 2015, 4:04 PM
This revision was automatically updated to reflect the committed changes.