[TIP] Best practices to maintain packages in CI environment
fuzzyman at voidspace.org.uk
Sun Oct 10 11:13:51 PDT 2010
On 10/10/2010 19:09, Marius Gedminas wrote:
> On Fri, Oct 08, 2010 at 04:50:54PM +0200, Alex wrote:
>> Our continous integration server (Hudson) controls several slave
>> machines (VM), each of which runs Python. Whenever a new package is
>> needed, I have to manually install the package in each slave and it's
>> very convenient since now I have 20 of them. I've thought of using
>> 'virtualenv' but it dramatically increases the build time when the
>> number of pacakge is large. What are the best approaches to deploy and
>> maintain these pacakges (version) in a build/testing farm ?
> virtualenv or zc.buildout.
So your answer to the original poster's difficulty with virtualenv is to
> Buildout is more featureful, but also more complicated and thus harder
> to learn/maintain. Some of its features, e.g. the shared egg cache, are
> very nifty if you need to set up dev environments for a bunch of
> packages that share some of their dependencies.
> Marius Gedminas
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
READ CAREFULLY. By accepting and reading this email you agree,
on behalf of your employer, to release me from all obligations
and waivers arising from any and all NON-NEGOTIATED agreements,
licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap,
confidentiality, non-disclosure, non-compete and acceptable use
policies ("BOGUS AGREEMENTS") that I have entered into with your
employer, its partners, licensors, agents and assigns, in
perpetuity, without prejudice to my ongoing rights and privileges.
You further represent that you have the authority to release me
from any BOGUS AGREEMENTS on behalf of your employer.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python