On Wed, Sep 17, 2008 at 4:59 PM, <kmradke_at_rockwellcollins.com> wrote:
>
> "Mark Phippard" <markphip_at_gmail.com> wrote on 09/17/2008 10:01:39 AM:
>> On Wed, Sep 17, 2008 at 10:53 AM, Julian Foad
>> <julianfoad_at_btopenworld.com> wrote:
>> > kmradke_at_rockwellcollins.com wrote:
>> >> Suppose one has access to some fairly beefy hardware on multiple
>> >> platforms (solaris x86, windows, linux) that have a fair number of
>> >> spare cycles.
>> >>
>> >> What does it take to become a buildbot?
>> >
>> > Me too! Only without the beefy hardware or the multiple platforms.
>>
>> Start here:
>>
>> http://svn.collab.net/repos/svn/trunk/tools/buildbot/slaves/README
>
> Thanks for the pointer. I should have been able to find that myself.
>
> But it confirms what I was afraid of. I would need to open up some
> machines more than our network overlords would like. I was hoping
> I could setup some type of nightly process which would then inform
> the buildbot master of the status via something less intrusive like
> email.
I have the same issue and I recall Lieven said that it can in fact be
done. He'd need to provide the details. I think your Buildbot just
needs to run when it wants to (can poll for changes of course) and
then it can send the results to the master.
I have machines that can be used as well and would also need this
feature. I tried setting this up in the run-up to 1.5 and could not
get Buildbot installed on RHEL. Just ran out of time and forgot about
it, but can take it up again.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-17 23:17:10 CEST