You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Julian Foad <ju...@btopenworld.com> on 2008/09/17 14:53:19 UTC
How to become a build-bot [was: Release Management for 1.6.x]
kmradke@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.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: How to become a build-bot [was: Release Management for 1.6.x]
Posted by km...@rockwellcollins.com.
Lieven Govaerts <sv...@mobsol.be> wrote on 09/18/2008 03:21:18 PM:
> Mark Phippard wrote:
> > On Wed, Sep 17, 2008 at 4:59 PM, <km...@rockwellcollins.com> wrote:
> ..
> >> 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.
> >
>
> There are two options basically:
> 1. you only run the slave at certain times of the day/night. The master
> will combine all outstanding jobs and trigger the slave as soon as it
> connects. Disadvantage is that there's no way as far as I know to stop
> the buildslave gracefully, so if there's a build in progress that
> results in a FAIL mail to svn-breakage. If you want to do one nightly
> build per slave, than I can schedule that at a certain time and you just
> make sure the slave is online at that time. Then you kill it 2 hours
> later so you're sure no build is in progress.
> Note that it's always the slave that connects to the master, over HTTP.
> No incoming connections need to be enabled. However, you are giving a
> remote software and person (ie. me) access to execute arbitrary shell
> commands in the slave environment.
>
> 2. you do not use a buildslave, but send the results of a build to
> svn-breakage. This was the pre-buildbot method, but AFAIC still valid.
> The scripts we used for those nightly builds are in
> trunk/tools/test-scripts@2560. They were deleted afterwards so probably
> not really up to date.
>
> I prefer option 1; but would be equally happy if you implement option 2.
Probably have to go with option #2. While the environment could
be locked down for #1, it still probably would not be authorized.
For #2, I'm thinking of just running a nightly build and email results
back.
Might take me awhile to look at the old scripts though...
Kevin R.
Re: How to become a build-bot [was: Release Management for 1.6.x]
Posted by Lieven Govaerts <sv...@mobsol.be>.
Mark Phippard wrote:
> On Wed, Sep 17, 2008 at 4:59 PM, <km...@rockwellcollins.com> wrote:
..
>> 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.
>
There are two options basically:
1. you only run the slave at certain times of the day/night. The master
will combine all outstanding jobs and trigger the slave as soon as it
connects. Disadvantage is that there's no way as far as I know to stop
the buildslave gracefully, so if there's a build in progress that
results in a FAIL mail to svn-breakage. If you want to do one nightly
build per slave, than I can schedule that at a certain time and you just
make sure the slave is online at that time. Then you kill it 2 hours
later so you're sure no build is in progress.
Note that it's always the slave that connects to the master, over HTTP.
No incoming connections need to be enabled. However, you are giving a
remote software and person (ie. me) access to execute arbitrary shell
commands in the slave environment.
2. you do not use a buildslave, but send the results of a build to
svn-breakage. This was the pre-buildbot method, but AFAIC still valid.
The scripts we used for those nightly builds are in
trunk/tools/test-scripts@2560. They were deleted afterwards so probably
not really up to date.
I prefer option 1; but would be equally happy if you implement option 2.
Lieven
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: How to become a build-bot [was: Release Management for 1.6.x]
Posted by Mark Phippard <ma...@gmail.com>.
On Wed, Sep 17, 2008 at 4:59 PM, <km...@rockwellcollins.com> wrote:
>
> "Mark Phippard" <ma...@gmail.com> wrote on 09/17/2008 10:01:39 AM:
>> On Wed, Sep 17, 2008 at 10:53 AM, Julian Foad
>> <ju...@btopenworld.com> wrote:
>> > kmradke@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@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: How to become a build-bot [was: Release Management for 1.6.x]
Posted by km...@rockwellcollins.com.
"Mark Phippard" <ma...@gmail.com> wrote on 09/17/2008 10:01:39 AM:
> On Wed, Sep 17, 2008 at 10:53 AM, Julian Foad
> <ju...@btopenworld.com> wrote:
> > kmradke@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.
Kevin R.
Re: How to become a build-bot [was: Release Management for 1.6.x]
Posted by Julian Foad <ju...@btopenworld.com>.
On Wed, 2008-09-17 at 11:01 -0400, Mark Phippard wrote:
> On Wed, Sep 17, 2008 at 10:53 AM, Julian Foad
> <ju...@btopenworld.com> wrote:
> > kmradke@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!
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: How to become a build-bot [was: Release Management for 1.6.x]
Posted by Mark Phippard <ma...@gmail.com>.
On Wed, Sep 17, 2008 at 10:53 AM, Julian Foad
<ju...@btopenworld.com> wrote:
> kmradke@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
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org