472921 - per-slave status on buildbot waterfalls

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Chris AtLee [:catlee]]

Attachment: enable per-slave status display

Here's a patch that gives per-slave status and build history from the buildbot waterfall.

It could probably be submitted upstream as well.

Comment 1

[[e-mail] (:bhearsum)]

Comment on attachment 356262 [details] [diff] [review]
enable per-slave status display

I'd really like to see this get upstream review. My policy has generally been not to apply core Buildbot patches unless they've landed upstream. This helps minimize pain when we import a new version.

Can you submit this upstream, please? Once it's committed up there we can apply it down here.

Comment 2

[Chris AtLee [:catlee]]

I attached this patch to upstream ticket 110: http://buildbot.net/trac/ticket/110

Comment 3

[Chris AtLee [:catlee]]

Attachment: enable per-slave status display

This was committed upstream

Comment 4

[Chris AtLee [:catlee]]

Comment on attachment 356947 [details] [diff] [review]
enable per-slave status display

Checking in buildbot/status/web/base.py;
/cvsroot/mozilla/tools/buildbot/buildbot/status/web/base.py,v  <--  base.py
new revision: 1.2; previous revision: 1.1
done
Checking in buildbot/status/web/build.py;
/cvsroot/mozilla/tools/buildbot/buildbot/status/web/build.py,v  <--  build.py
new revision: 1.2; previous revision: 1.1
done
Checking in buildbot/status/web/builder.py;
/cvsroot/mozilla/tools/buildbot/buildbot/status/web/builder.py,v  <--  builder.py
new revision: 1.2; previous revision: 1.1
done
Checking in buildbot/status/web/slaves.py;
/cvsroot/mozilla/tools/buildbot/buildbot/status/web/slaves.py,v  <--  slaves.py
new revision: 1.2; previous revision: 1.1
done

Comment 5

[Chris AtLee [:catlee]]

Live on production now.  Woohoo!