Closed Bug 1169766 Opened 5 years ago Closed 1 year ago
[ETL] Start pipeline with raw buildbot Pulse messages?
ActiveData's translation matrix looks like the inverse of pulsetranslator's translation matrix! ActiveData is quite agnostic about property values and may not require the cleanup that pulsetranslator provides. Furthermore, ActiveData's ETL pipeline records all raw pulse messages, enabling reprocessing in the event of errors and changes. Maybe ActiveData should feed off the raw buildbot messages? We could have a system that does a daily copy of pulsetranslator's messageparams.py to effectively steal the core intellegence, and stay up to date.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.