2009/10/25 "Martin v. Löwis" <martin at v.loewis.de>: >> I've been trying to get some feedback about firing up buildbots on Cloud >> Servers for a while now and haven't had much luck. I'd love to find a >> way of having buildbots come to life, report to the mother ship, do the >> build, then go away 'till next time they're required. > > I'm not quite sure whom you have been trying to get feedback from, and > can't quite picture your proposed setup from above description. Sorry, feedback was the wrong word. I've been digging round the documentation I've been able to find and looking into what's needed to set up a slave. > In any case, ISTM that your approach isn't compatible with how buildbot > works today (not sure whether you are aware of that): a build slave > needs to stay connected all the time, so that the build master can > trigger a build when necessary. > > So if your setup requires the slaves to shut down after a build, I don't > think this can possibly work. It's not so much that I *require* the slave to shut down, more that I'm not sure how well I'll be able to ensure that it's up all the time, and I'm trying to understand the implications of that. My basic impression is that it's not really going to work, unfortunately. Paul.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4