#1771: Store 'slavename' in the database for every build
-------------------------+-----------------------
Reporter: jhopkinsmomo | Owner:
Type: undecided | Status: new
Priority: major | Milestone: undecided
Version: 0.8.2 | Keywords:
-------------------------+-----------------------
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.
--
Ticket URL: <http://trac.buildbot.net/ticket/1771>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
