[Buildbot-commits] [Buildbot] #1771: Store 'slavename' in the database for every build

[Buildbot trac]

#1771: Store 'slavename' in the database for every build
-------------------------+---------------------
Reporter:  jhopkinsmomo  |       Owner:  shar
    Type:  enhancement   |      Status:  closed
Priority:  major         |   Milestone:  0.9.0
 Version:  0.8.2         |  Resolution:  fixed
Keywords:  database      |
-------------------------+---------------------
Changes (by dustin):

 * status:  accepted => closed
 * resolution:   => fixed


Old description:

> The 'slavename' property is only set for a small fraction of buildsets,
> so from what I can tell, for most builds there is no way to know which
> build slave it was run on (using only the database).  This is a hindrance
> to writing reporting queries.
>
> I'm also wondering if the slavename should be set further down the table
> hierarchy - at the "builds" or "buildrequests" level.  My own preference
> would be to add a 'slavename' field to the builds table.

New description:

 The 'slavename' property is only set for a small fraction of buildsets, so
 from what I can tell, for most builds there is no way to know which build
 slave it was run on (using only the database).  This is a hindrance to
 writing reporting queries.

 I'm also wondering if the slavename should be set further down the table
 hierarchy - at the "builds" or "buildrequests" level.  My own preference
 would be to add a 'slavename' field to the builds table.

--

Comment:

 Yep, builds now have a buildslaveid, in nine.

-- 
Ticket URL: <http://trac.buildbot.net/ticket/1771#comment:7>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation