Lieven Govaerts <svnlgo_at_mobsol.be> wrote on 09/18/2008 03:21:18 PM:
> Mark Phippard wrote:
> > On Wed, Sep 17, 2008 at 4:59 PM, <kmradke_at_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_at_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
Might take me awhile to look at the old scripts though...
Received on 2008-09-19 18:15:53 CEST