Right now we don't send enough information the build started Pulse messages to match up the Build to its BuildRequest. If consumers need to do that, they need to have access to the Scheduler database and run a relatively expensive query (matching on claimed_by_name, claimed_by_incarnation, builder name, build number, and complete=0) to find them. There's nothing that strictly _requires_ this right now, but having it available to things like the Buildbot Bridge would almost certainly lower load on the Buildbot schedulerdb.
I believe this got added at some point.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WORKSFORME
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.