On Wed, Jul 18, 2018 at 12:22 AM Volker Braun <vbraun.n...@gmail.com> wrote: > > The buildbot master config isn't public since it includes the worker > passwords. Though I think the worst case means somebody can submit incorrect > build results. Still, there wasn't much need to make the config public. If > you want to have it I'm happy to send you an archive. More interesting are > probably my notes on setting up a buildbot worker. Just send me the worker > name and password and I'll be happy to have the buildbot dish out tasks...
Thanks; I know that if I could get that set up (that is the big "if" currently, though I think we'll have a solution soon) you would be happy to add it to the fleet. However, the below information doesn't answer my question. I know how to set up a buildbot worker as I run some for other projects. I explicitly want to know how the builds are configured to ensure that they make sense for my platform of concern, which might require additional steps, etc. There's no good reason to have passwords stored directly in the master.cfg. It's just a Python module and can import worker-specific data from a separate config file that is not committed to version control (or at least to a public repo). Passwords and things like that can even be in a separate JSON file or something like that. There's also a secrets feature which, granted, is pretty new. See for example https://github.com/python/buildmaster-config Also the below information is a bit outdated--it's called buildbot-worker now; see http://docs.buildbot.net/current/manual/installation/installation.html#installation-from-pypi http://docs.buildbot.net/current/manual/installation/worker.html Also, this documentation should at least be on the wiki at https://wiki.sagemath.org/buildbot -- if we agree that having a buildbot for a platform is necessary for a platform to be "supported", it should be well-documented how to do this easily (see again, for contrast https://devguide.python.org/buildworker/). I'd be happy to help with that if I had more info on how the master is configured. Thanks, E > Setting up a Buildbot Slave > --------------------------- > > Create a separate account to run the buildbot slave. This is where > Sage will be compiled and tested. Then, install the buildbot > slave. The easiest way is using pip: > > pip install buildbot-slave > > For the buildslave configuration, we will put everything into the > ~/slave directory: > > buildslave create-slave -r --umask=022 ~/slave \ > build.sagemath.org:9990 NAME SLAVE_PASS > > Replace NAME with a short name (no spaces) and pick a random > SLAVE_PASS. Then edit ~/slave/info as appropriate. To start the > buildbot slave, run > > buildslave start slave > > The last arument is the directory name. > > > > > On Tuesday, July 17, 2018 at 12:37:56 PM UTC+2, Erik Bray wrote: >> >> Does anyone know where it lives? Is there a repository for it? I was >> thinking it should be under github.com/sagemath but nothing stands >> out. >> >> I would like to try to set up a buildbot, but it's unclear exactly >> *how* to do that when I don't even know what the builder >> configurations are (knowing how buildbot works one could say that in >> theory it's not necessary to know; but also knowing how "difficult" >> sage can be, I want to make sure the environment has everything it >> needs... > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
