[Buildbot-devel] Some questions

[Dennis Schridde]

Did no one recieve this email, or are there simply no answers possible?
(I had quite some problems with it not arriving that the list, and last time I 
checked SourceForge still didnt show it in its archives, so maybe there is a 
transportation error at fault.)

Am Samstag, 7. Juni 2008 22:59:46 schrieb Dennis Schridde:
> Hi!
>
> We are using Buildbot since a few days and have some questions:
>
> - How is buildbot.scheduler.Scheduler(isFileImportant) supposed to work?
> I tried the following, but without luck (the build is never triggered):
> def importantQuickFiles(filename):
>     return (filename.endswith(".c") or filename.endswith(".h") or
>         filename.endswith(".cpp") or filename.endswith(".hpp") or
>         filename.endswith(".am") or filename.endswith(".ac"))
> c['schedulers'] = []
> from buildbot import scheduler
> c['schedulers'].append(scheduler.Scheduler(name="quick", branch=None,
>     treeStableTimer=10*60,
>     fileIsImportant=importantQuickFiles,
>     builderNames=['quick_linux', 'quick_mingw32']))
>
>
> - I get a weird backtrace in twistd.log, but dont know what creates it and
> whether it should be there. (attached)
> buildbot-0.7.7
> twisted-2.4.0
> twisted-mail-0.3.0
> twisted-names-0.3.0
> twisted-web-0.6.0
> twisted-words-0.4.0
> python-2.5.2
>
>
> - How can I make buildbot.status.words.IRC announce failed builds into a
> channel? Currently it just sits there and reacts to queries.
>
>
> - What is the default for haltOnFailure and warnOnWarnings, etc
> (BuildStep)?
>
>
> - Can I add commands before ./configure in
> buildbot.process.factory.GNUAutoconf ? addStep just seems to be able to
> append, but not prepend.
>
>
> - Can multiple buildbot.steps.source.SVN with mode=copy share a source
> directory? (Or not have one at all, if the svn server is local and can be
> accessed through file:/// anyway?)
>
>
> - Finally what I assume is probably a feature request:
> Is it possible for buildslave admins to verify the commands their slaves
> will be running?
> Currently, if someone would takeover the master (or just make a mistake in
> configuration), this would immediately spread over all the slaves, possibly
> causing damage of some form.
>
> What I currently have in mind is that when the buildslave recieves a set of
> commands to run, it checksums it and compares that with a checksum stored
> in buildbot.tac. The build would only be run if the checksums match.
> If they do not match, it fires an email (to the master/notifiers, or the
> slave admin in case his emailaddress is known).
> That email would include the new commands to be run, and their checksum,
> plus the request to please run "buildbot confirm-build /path checksum" in
> case the commands are correct.
> The checksum stored there could have some special values (real values
> depending on the checksuming algorithm, of course):
> 0: Never confirmed anything, confirmation request will always be send.
> -1: Opted out of confirmation. Treat as if checksums always match.
> The latter would be the default for migrated setups.
>
> Thanks in advance,
> Dennis


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://buildbot.net/pipermail/devel/attachments/20080620/b78bbd29/attachment.bin>