[TIP] "midget" pony continuous integration tool
lists at durin42.com
Wed May 6 06:22:54 PDT 2009
On May 5, 2009, at 5:58 PM, Noah Gift wrote:
> On Wed, May 6, 2009 at 10:28 AM, Doug Latornell <doug at sadahome.ca>
>> I put a wrapper around Jeff Winkler's Nosy script that gives it a
>> line parser and a configuration file. It would limit your "builds"
>> to only
>> triggering when there are source changes. You can pass the --with-
>> in the options item of the config file. And you get the ability to
>> your "build" on the fly if you include the config file in the list
>> of files
>> that are monitored for changes.
>> Details at: http://douglatornell.ca/software/python/Nosy/
>> Source at: http://douglatornell.ca/software/python/Nosy-1.0.tar.gz
> Thanks, this might be a good midget pony in a pinch.
If you're on OS X, also check out shepherd, which uses FSEvents so
there won't be any disk polling:
>> On Tue, May 5, 2009 at 12:57 PM, Noah Gift <noah.gift at gmail.com>
>>> While I am waiting for Titus to build his proper CI pony, I was
>>> wondering if anyone has any "midget" ponies laying around. I am in
>>> deadline mode for the next month and can't justify setting up a
>>> buildbot, but am thinking about just running:
>>> while True:
>>> nosetests --with-coverage
>>> Anyone else have a better midget pony?
>>> testing-in-python mailing list
>>> testing-in-python at lists.idyll.org
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
More information about the testing-in-python