Josh Berkus wrote:
I am expecting that for the most part people will want the lists of
state changes, rather than the lists of all builds or failures. Will
Spikesource tests track state changes?
They'd like to. CVS makes this kind of challenging. They'd be happy to
have suggestions ...
In the buildfarm system, the state of each machine/branch is either OK
or the stage in the buildfarm process that failed - we stop at the first
such failure. Since all the data reported is stored in our db, finding
the previous state is fairly simple - we just run this:
select coalesce(
(select distinct on (snapshot) stage
from build_status
where sysname = ? and branch = ? and snapshot < ?
order by snapshot desc
limit 1),
'NEW') as prev_status
plugging in the values from the current build.
BTW, these list are being set up only for announcements, so I would have
to grant permission before any results started flowing.
Yep, that's why I'm mentioning it.
send me details off-list.
cheers
andrew
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
