On Sun, Dec 25, 2005 at 12:54:32PM -0500, Tim Peters wrote:
This really helps at Zope Corp. One downside is that we seem unable
to get an in-house Windows buildbot slave to work reliably, and so far
don't even know whether that's because of Windows, the buildbot code,
or flakiness in our
Tim Peters wrote:
Someone sets up a buildbot master
That's what I now did:
http://www.python.org/dev/buildbot/
I'm not quite sure on a number of concepts: should there
be multiple slaves per builder? Should I have multiple
factories? How should I pass build-machine specific information
(like:
On Wed, 28 Dec 2005 17:43:04 +0100, \Martin v. Löwis\ [EMAIL PROTECTED]
wrote:
Tim Peters wrote:
Someone sets up a buildbot master
That's what I now did:
http://www.python.org/dev/buildbot/
I'm not quite sure on a number of concepts: should there
be multiple slaves per builder? Should I have
Jean-Paul Calderone wrote:
A slave is an entity capable of performing tasks. It can be
asked to perform any task you like, though it may not be able
to perform them all if it lacks some requirements.
This is clear in principle. However, what constitutes a task?
I see that you can send it
Jean-Paul Calderone wrote:
I guess the config for this particular behavior would look something
like...
You were right that I needed two schedulers for that.
Unfortunately, it doesn't work at all, because svn_buildbot.py does
not report branches on which a change happened, so if you have
[Martin v. Löwis]
...
Unfortunately, it doesn't work at all, because svn_buildbot.py does
not report branches on which a change happened, so if you have multiple
schedulers for a subversion source, they either all build when a change
occurs, or none of them.
If svn_version knew about
Take a look at:
http://buildbot.zope.org/
That runs code from:
http://buildbot.sourceforge.net/
Someone sets up a buildbot master (that's what the Zope URL points
at), and then any number of people can volunteer to set up their boxes
as buildbot slaves. From time to time the buildbot
On 12/25/05, Tim Peters [EMAIL PROTECTED] wrote:
Take a look at:
http://buildbot.zope.org/
That runs code from:
http://buildbot.sourceforge.net/
Someone sets up a buildbot master (that's what the Zope URL points
at), and then any number of people can volunteer to set up their
On Sunday 25 December 2005 15:23, Brett Cannon wrote:
As in some machine I might personally have left on? That would
require a static IP which I don't know how common that will be. But
Only buildbot masters are required to have resolvable names (not necessarily
static, though it helps;
[Tim]
Take a look at:
http://buildbot.zope.org/
That runs code from:
http://buildbot.sourceforge.net/
Someone sets up a buildbot master (that's what the Zope URL points
at), and then any number of people can volunteer to set up their boxes
as buildbot slaves.
[Brett]
As in
On 12/25/05, Tim Peters [EMAIL PROTECTED] wrote:
[Tim]
Take a look at:
http://buildbot.zope.org/
That runs code from:
http://buildbot.sourceforge.net/
Someone sets up a buildbot master (that's what the Zope URL points
at), and then any number of people can volunteer to
On Sun, 25 Dec 2005 16:54:44 -0800, Brett Cannon [EMAIL PROTECTED] wrote:
On 12/25/05, Tim Peters [EMAIL PROTECTED] wrote:
[Tim]
Take a look at:
http://buildbot.zope.org/
That runs code from:
http://buildbot.sourceforge.net/
Someone sets up a buildbot master (that's what
Brett As in some machine I might personally have left on? That would
Brett require a static IP which I don't know how common that will be.
Nah, just use dyndns.org.
Skip
___
Python-Dev mailing list
Python-Dev@python.org
13 matches
Mail list logo
