Confirmed users
1,927
edits
Auto-tools/Projects/Pulse: Difference between revisions
Jump to navigation
Jump to search
m
→Consuming Buildbot messages: pulse -> Pulse
(→Consuming Buildbot messages: a few edits) |
m (→Consuming Buildbot messages: pulse -> Pulse) |
||
| Line 187: | Line 187: | ||
Another advantage of the NormalizedBuildConsumer is that it will only publish messages for a given build or test job after the logs for that job are available; using the BuildConsumer directly can result in the reception of messages for a build before the build artifacts are available, which can cause problems in consumers if they don't explicitly guard against this. | Another advantage of the NormalizedBuildConsumer is that it will only publish messages for a given build or test job after the logs for that job are available; using the BuildConsumer directly can result in the reception of messages for a build before the build artifacts are available, which can cause problems in consumers if they don't explicitly guard against this. | ||
Generally speaking, consumers that wish to be notified when specific build or test jobs are completed should use the NormalizedBuildConsumer; consumers that need direct access to the Buildbot | Generally speaking, consumers that wish to be notified when specific build or test jobs are completed should use the NormalizedBuildConsumer; consumers that need direct access to the Buildbot Pulse stream or are looking for non-specific jobs (such as all jobs belonging to a particular commit) should probably use the BuildConsumer. | ||
= Road Map = | = Road Map = | ||