On Tue, Nov 15, 2016 at 9:20 AM, Chris Kees <[email protected]> wrote:
> Hi, > > I had been running buildbot in the 0.8.x range (no docker containers and > workers running on different physical machines). I now have the > docker-based tutorial up and running with a modified master.cfg and worker > container. I really like that set up and plan to expand my set of workers > to include some other distributions. Couple of questions: > > How do I add back in my old workers that live on real platforms? Does that > defeat the purpose of the docker setup? > > OK, partially answering my own questions here. You can open up the port for the workers to communicate. I guess it defeats the purpose of minimizing the number of open ports, but it seems like that's the only way if you need remote workers. > I would also like to enable ssl on the website and user-based > authentication because I can't allow arbitrary users to trigger builds. My > old config section with authz doesn't work, but I think it may be minor api > change from 0.8-0.9. > > The github oath was easy to transition to--really like that feature. It would be nice if it was aware of github teams. > Is it possible with the docker approach to put the master.cfg on the local > machine so it's not exposed on a public repo? > > I worked around this by using local environment variables to pass in any sensitive information. > Thanks, > Chris >
_______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
