[issue13124] Add "Running a Build Slave" page to the devguide

Stefan Krah added the comment: Here's a terse shell script that IMO even moderately experienced admins will prefer to the current version. I'm not sure if the devguide is the right place for this, since non-devs are very welcome to set up buildbots. -- nosy: +pitrou Added file: http://

[issue13124] Add "Running a Build Slave" page to the devguide

Changes by Stefan Krah : Added file: http://bugs.python.org/file24399/buildslave_install.txt ___ Python tracker ___ ___ Python-bugs-list maili

[issue13124] Add "Running a Build Slave" page to the devguide

Changes by Stefan Krah : Removed file: http://bugs.python.org/file24398/buildslave_install.txt ___ Python tracker ___ ___ Python-bugs-list mai

[issue13124] Add "Running a Build Slave" page to the devguide

Antoine Pitrou added the comment: > Here's a terse shell script that IMO even moderately experienced admins > will prefer to the current version. I'm sure some admins will prefer using their system's packages (I think buildbot is packaged for Debian/Ubuntu, I see it in Mageia's packages, not su

[issue13124] Add "Running a Build Slave" page to the devguide

Stefan Krah added the comment: Antoine Pitrou wrote: > I'm sure some admins will prefer using their system's packages (I think > buildbot is packaged for Debian/Ubuntu, I see it in Mageia's packages, > not sure about Fedora). Yes, certainly. I had a bad experience using the packaged buildbot-s

[issue13124] Add "Running a Build Slave" page to the devguide

Eric Snow added the comment: No problem, Stefan. :) The main motivation was to capture the discussion at the time so that something actually came of it. Adding info to the devguide, essentially the catalog/how-to of core dev activities, was meant to simply provide another clear avenue for t

[issue13124] Add "Running a Build Slave" page to the devguide

Stefan Krah added the comment: Eric Snow wrote: > Incidentally, the second patch is a bit cleaner than the first. Yes, indeed it is. :) To prevent a misunderstanding: In my last mail I was talking about the "Build Slaves and Security" additions to: http://wiki.python.org/moin/BuildBot --

[issue13124] Add "Running a Build Slave" page to the devguide

New submission from Eric Snow : Here's a patch to add a page to the devguide on running a build slave. I copied pretty liberally from the wiki (http://wiki.python.org/moin/BuildBot). That page may or may not be up to date (I don't know), so the bulk of this new page may also be out of date..

[issue13124] Add "Running a Build Slave" page to the devguide

Ezio Melotti added the comment: A few comments: * are you following some convention about the spelling of buildbot/Buildbot/BuildBot? * "+3. the standard development toolchain." Which is? I think a compiler is the only missing bit. * "(in which case you'll have to install Python and T

[issue13124] Add "Running a Build Slave" page to the devguide

Eric Snow added the comment: Great feedback! Keep in mind that nearly all the content in my patch is pulled unedited from either the wiki page and the python-dev thread I mentioned. I'll work on cleaning it up when I get a chance (probably after Wednesday's PyCon CFP closes :). If anyone wa

[issue13124] Add "Running a Build Slave" page to the devguide

Stefan Krah added the comment: I think the whole security paragraph should be deleted. The discussion on python-dev has overstated the risks. Anyone who is *that* security conscious and in effect does not trust the Python committers should also audit the thousands of lines of ./configure and an

[issue13124] Add "Running a Build Slave" page to the devguide

Eric Snow added the comment: Per Ezio's and Stefan's feedback I cleaned things up a little: * consolidated on "Buildbot" * clarified the meaning of the "standard development toolchain" * % changed to $ * cleaned up the network ports section * removed a bunch of outdated/unnecessary info I did

[issue13124] Add "Running a Build Slave" page to the devguide

Changes by Eric Snow : Added file: http://bugs.python.org/file23479/devguide-buildbots-2.diff ___ Python tracker ___ ___ Python-bugs-list mail

[issue13124] Add "Running a Build Slave" page to the devguide

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue13124] Add "Running a Build Slave" page to the devguide

Brett Cannon added the comment: Did you want to commit this patch yourself, Eric, since you have commit privs now? -- ___ Python tracker ___

[issue13124] Add "Running a Build Slave" page to the devguide

Eric Snow added the comment: Yeah, at some point I will. :) I've been pretty focused on implementing a C-OrderedDict, which I'm (hopefully) wrapping up pretty soon. Once that happens I'm going to revisit a bunch of the open tickets I have. If you want to push this sooner than that, feel fre

[issue13124] Add "Running a Build Slave" page to the devguide

Eric Snow added the comment: Looking this over, it seems like there were outstanding objections to adding this to the devguide and to the content. I still think the devguide is the right place and that something like my second patch would be appropriate. Before I take any time to update the p

[issue13124] Add "Running a Build Slave" page to the devguide

Stefan Krah added the comment: Eric Snow wrote: > Looking this over, it seems like there were outstanding objections to adding > this to the devguide and to the content. I have no issues with the content of the second patch. However, snakebite has changed the situation a little: We don't need

[issue13124] Add "Running a Build Slave" page to the devguide

Ezio Melotti added the comment: > Before I take any time to update the patch, does anyone object > to the location or intent of the changes? Adding a new page to the devguide seems OK to me. It makes the devguide bigger, but it can easily be ignored by developers/contributors if they are not