Ticket #1771 (accepted enhancement)

Opened 2 years ago

Last modified 4 months ago

Store 'slavename' in the database for every build

Reported by: jhopkinsmomo Owned by: shar
Priority: major Milestone: 0.9.0
Version: 0.8.2 Keywords: database
Cc: sharan.monikantan@…

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.

Change History

comment:1 Changed 2 years ago by dustin

  • Keywords database added
  • Type changed from undecided to enhancement

comment:2 Changed 2 years ago by ayust

  • Milestone changed from undecided to 0.8.4

comment:3 Changed 2 years ago by dustin

  • Milestone changed from 0.8.4 to 0.8.5

Schema change -> 0.8.5

comment:4 Changed 8 months ago by dustin

  • Milestone changed from 0.8.+ to 0.9.0

This will happen in 0.9.0 (we'll have a buildslaves table)

comment:5 Changed 4 months ago by dustin

Adding a buildslaves table and data API resource type is one of the outstanding items in the nine project right now:

 https://github.com/buildbot/buildbot/blob/nine/README.md

comment:6 Changed 4 months ago by shar

  • Cc sharan.monikantan@… added
  • Owner set to shar
  • Status changed from new to accepted
Note: See TracTickets for help on using tickets.