Confirmed users
194
edits
Zeller
Joined 28 June 2013
→Bug 1032978 - Add a standalone process that listens to pulse for release related buildbot messages
| Line 66: | Line 66: | ||
* Should I be using a different consumer like BuildConsumer? NormalizedBuildConsumer will miss some builds, pulsetranslator has a hardcoded list of recognized platforms, and will drop others. http://hg.mozilla.org/automation/mozillapulse/file/default/mozillapulse/consumers.py | * Should I be using a different consumer like BuildConsumer? NormalizedBuildConsumer will miss some builds, pulsetranslator has a hardcoded list of recognized platforms, and will drop others. http://hg.mozilla.org/automation/mozillapulse/file/default/mozillapulse/consumers.py | ||
** Dump out the full message stream for a while until you see one of the ones you care about. | ** Dump out the full message stream for a while until you see one of the ones you care about. | ||
* Should we send the concat'd data instead of payload, and have the common_keys listed in the REST API and hold all the logic for the None's and such there? | |||
** No because the API should only be hit with messages we care about, and so should be filtered before ever propagating a POST request to the REST API | |||
==== To Do ==== | ==== To Do ==== | ||