[Buildbot-devel] executing steps on a windows slave that does not have buildbot slave software installed

Philippe McLean philippe.mclean at gmail.com
Fri Jun 7 01:01:12 UTC 2013

that sounds like a plan, thanks. with powershell remoting, any issues with
getting command output, flakiness, timeouts, blocking due to file handles...

On Thu, Jun 6, 2013 at 4:06 PM, Dan Kegel <dank at kegel.com> wrote:

> On Thu, Jun 6, 2013 at 4:02 PM, Philippe McLean
> <philippe.mclean at gmail.com> wrote:
> > my goal is to deploy "production-like" slaves with no configuration, run
> the
> > setup installers, install the build, reboot, run functional tests,
> > acceptance tests.
> >
> > the main thing is that buildbot should not be on a production machine,
> > although python would be.
> >
> > something like wmic (can it accept password as an argument?) or
> powershell
> > remote execution...
> So these are test-only slaves on which you install the result of a build,
> and then run functional tests?
> That's starting to sound kind of doable.   The first step would be to do
> all
> that without buildbot.   Once you have it down to a slick set of three or
> four commandlines (to copy over the files, unpack them, and run a test
> script),
> and can do that with wmic or powershell, then just add those
> three or four commandlines to a script you start from a buildbot
> on a different machine.
> - Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20130606/e08797de/attachment.html>

More information about the devel mailing list