[Buildbot-devel] adding historical plots like chromium's buildbot
Philip Winston
pwinston at gmail.com
Sun Oct 13 16:05:14 UTC 2013
Chromium's buildbot has cool performance plots:
http://build.chromium.org/f/chromium/perf/dashboard/overview.html
The client part, the javascript, is BSD license so I grabbed it, and that
works fine. It runs off .dat files which are json.
I'm planning to have a tree in perforce for plots like:
data/performance/fooTest.dat
data/performance/barTest.dat
data/exeSize/productA.dat
data/exeSize/productB.dat
data/index.html
Builders would update these .dat files with new lines of data.
But how to serve this stuff? see 3 options:
1) Map these tree into public_html, and update it with a builder. This
strikes me as a little weird because today our master.cfg and other master
files are in perforce, but they are NOT synced except when we restart the
buildbot. So this would be adding a subdir which IS synced somehow, with a
separate builder and separate overlayed/nested perforce workspace. Just
seems a bit confusing.
2) Keep the builder which just syncs the tree separate, sync it to a
separate location on the master. But then use a buildbot HtmlResource to
make http://buildbot/plots redirect to this other location. Like a symlink
basically (but we are on windows).
3) Use apache or some other server to serve the files. It would serve out
of a directory which was synced by a builder. We have buildbot on port 80
so add buildbot:8000 which is the plots.
4) Improve on 3 and put apache on port 80, then have a proxy which goes to
the buildbot so http://buildbot/waterfall would be the normal buildbot and
http://buildbot/plots would be the performance plots.
A possibly related question. Aside from these plots we might have a new
type of resource that times a few seconds to compute. Would using apache be
better for that, because we don't want to hang the whole buildbot if we
start doing more web stuff.
We are using buildbot 0.7.10, with perforce, on Windows. We have only about
10 users of the buildbot waterfall pages. Upgrading buildbot has been our
list for years, but it works perfectly for us there has been no reason to.
Thanks for any ideas. I setup our buildbot like 6 years ago but haven't
really been involved with it recently, now I'm trying to add these plots.
-Philip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20131013/3bba9bc2/attachment.html>
More information about the devel
mailing list