Ticket #1771 (accepted enhancement)
Store 'slavename' in the database for every build
|Reported by:||jhopkinsmomo||Owned by:||shar|
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.
- Keywords database added
- Type changed from undecided to enhancement