Create new job in ExecDB, and submit data gathered from the FedMsg.
Details
Details
- Reviewers
tflink mkrizek - Maniphest Tasks
- T307: Support global UUIDs throughout taskotron
- Commits
- rTRGR01a9ddd357cc: Initial support for ExecDB
Tested locally, and currently running at taskotron-demo
Diff Detail
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.
Comment Actions
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 | |
| 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). | |
I wonder if we should be keeping these names consistent throughout our code - libtaskotron is execdb_server