[Buildbot-devel] Buildbot-devel Digest, Vol 30, Issue 11
yuqian
yuqian at redoffice.com.cn
Fri Oct 24 09:19:30 UTC 2008
2008-10-24
yuqian
发件人： buildbot-devel-request at lists.sourceforge.net
发送时间： 2008-10-23 16:52:13
收件人： buildbot-devel at lists.sourceforge.net
抄送：
主题： Buildbot-devel Digest, Vol 30, Issue 11
Send Buildbot-devel mailing list submissions to
buildbot-devel at lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/buildbot-devel
or, via email, send a message with subject or body 'help' to
buildbot-devel-request at lists.sourceforge.net
You can reach the person managing the list at
buildbot-devel-owner at lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Buildbot-devel digest..."
Today's Topics:
1. Sporadic execeptions on Waterfall (Christian Lins)
2. buildbot caching config file (Jimmy John)
3. Re: buildbot caching config file (Greg Ward)
4. SetProperty extract_fn error handling (Brian Fallik)
5. one slave... for multiple masters? (john gale)
----------------------------------------------------------------------
Message: 1
Date: Thu, 16 Oct 2008 16:20:53 +0200
From: Christian Lins <Christian.Lins at Sun.COM >
Subject: [Buildbot-devel] Sporadic execeptions on Waterfall
To: Buildbot-devel at lists.sourceforge.net
Message-ID: <48F74DC5.1090404 at sun.com >
Content-Type: text/plain; charset="iso-8859-1"
Hi list!
I added a new Builder and reconfigured the Master (Buildbot-0.7.9), but
after that I sporadically get an exception when visiting the Waterfall
page (see attached stacktrace).
I'm fairly helpless... :-)
Thanks,
Christian
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Mon, 20 Oct 2008 10:46:54 -0700 (PDT)
From: Jimmy John <jimmyj_in at yahoo.com >
Subject: [Buildbot-devel] buildbot caching config file
To: buildbot-devel at lists.sourceforge.net
Message-ID: <782372.43708.qm at web50010.mail.re2.yahoo.com >
Content-Type: text/plain; charset=us-ascii
Hello,
I have a buildbot setup that runs every night at 1:00 am. One of the steps is to pull down a log file from the slave and place it in a dir corresponding to the current date. e.g
today = datetime.datetime.today()
destfilename_part = "~/xxx/summary_logs/%d-%d-%d/summary_reports_3_2_branch_test___%s" % (today.year, today.month, today.day, builder_name)
f.addStep(FileUpload(slavesrc="summary_reports.log" ,
masterdest=WithProperties(destfilename_part + "___%s.log" , "buildnumber"),
workdir= "../../"))
The problem is that when buildbot starts up, it seems to have computed destfilename_part correctly, but it caches it. So every night, the reports get dumped into the directory corr to the date when buildbot master was started. It does not compute destfilename_part afresh at each run.
Is there any way to have buildbot force to reread and recompute it's config file? or do I need to set up a cron job where I restart the master at say 12:00 midnight, so when it runs at 1:00 am it has the correct value of date within destfilename_part.
Thanks
Jimmy
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
------------------------------
Message: 3
Date: Mon, 20 Oct 2008 14:04:32 -0400
From: Greg Ward <gerg.ward+buildbot at gmail.com >
Subject: Re: [Buildbot-devel] buildbot caching config file
To: buildbot-devel at lists.sourceforge.net
Message-ID: <20081020180432.GB5905 at intelerad.com >
Content-Type: text/plain; charset=us-ascii
On 20 October 2008, Jimmy John said:
> I have a buildbot setup that runs every night at 1:00 am. One of the
> steps is to pull down a log file from the slave and place it in a dir
> corresponding to the current date. e.g
Are you sure you need to do this? Buildbot is very good at keeping
track of build logs, getting them from the slave to the master, serving
them up via HTTP, etc. Fundamentally, Buildbot is just an engine for 1)
the master telling the slave "run this command" and 2) getting the
output of that command back to the master. Sounds like you are
partially reinventing this wheel.
(If you have build steps that write to their own log files rather than
stdout/stderr, there is even a way to tell Buildbot about it, so it can
track/transfer those logs too. I can't remember if it's a simple
constructor arg to BuildStep or something more involved, but I believe
it is documented.)
Finally, remember that every log tracked by Buildbot has its own URL
that will return a copy of the log via HTTP.
> The problem is that when buildbot starts up, it seems to have computed
> destfilename_part correctly, but it caches it. So every night, the
> reports get dumped into the directory corr to the date when buildbot
> master was started. It does not compute destfilename_part afresh at
> each run.
Right, because your "config" file is just a bunch of Python code that is
executed *once*, when Buildbot starts. (This is a common source of
confusion.) You need a way to defer execution of that
datetime.datetime() call. Offhand, I'd say you're better off avoiding
the whole situation simply by taking advantage of Buildbot's
infrastructure for dealing with build logs.
Greg
------------------------------
Message: 4
Date: Mon, 20 Oct 2008 14:04:39 -0400
From: "Brian Fallik" <bfallik at litl.com >
Subject: [Buildbot-devel] SetProperty extract_fn error handling
To: buildbot-devel at lists.sourceforge.net
Message-ID:
<29883f290810201104r7d8b8442rc29dd222b7c8a0aa at mail.gmail.com >
Content-Type: text/plain; charset=ISO-8859-1
What is the correct error handling procedure for the extract_fn
callback parameter to SetProperty? In the event that the return code
from the command is non-zero, how do I signal that failure to the
buildbot and abort the build? My uneducated guess is to throw some
kind of exception from extract_fn, but this is just a guess.
Thanks,
brian
------------------------------
Message: 5
Date: Thu, 23 Oct 2008 00:42:53 -0700
From: john gale <john at smadness.com >
Subject: [Buildbot-devel] one slave... for multiple masters?
To: BuildBot Devel <buildbot-devel at lists.sourceforge.net >
Message-ID: <E3AEC928-122B-4E70-883D-5798463062BF at smadness.com >
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
I've been thinking a lot about creating a pool of machines to use for
many projects. Similar to the over-used "cloud computing" concept,
you would be able to create one master per overarching project, and
then have a pool of build and test slaves that can be allocated based
on who needs them.
There are ways to do this clumsily; say, set up multiple configuration
files on each slave, pointing to each different master.
But is there a way to do this more gracefully? Specifically, I don't
want people stepping on each others' toes. When one slave is being
used for testing, it can't host any other projects' unit tests. Very
much like the SlaveLock feature... except I'm hoping across multiple
masters.
There might not be a way to do this currently, but does it look like
it could be feasible? I don't have time now, but soon may be able to
devote some serious resources to this problem.
thanks,
~ john
=================
support the arts!
www.smadness.com
updated October 12, 2005
------------------------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
------------------------------
_______________________________________________
Buildbot-devel mailing list
Buildbot-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/buildbot-devel
End of Buildbot-devel Digest, Vol 30, Issue 11
**********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20081024/33e317a5/attachment.html>
More information about the devel
mailing list