[TIP] Best practices to maintain packages in CI environment
olemis at gmail.com
Fri Oct 15 06:53:57 PDT 2010
On Fri, Oct 15, 2010 at 8:52 AM, Olemis Lang <olemis at gmail.com> wrote:
> On Fri, Oct 8, 2010 at 9:50 AM, Alex <alex.pubblico.profilo at gmail.com> 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 ?
> What I usually do (*LOCALLY*) is to copy all sdists I'm gonna under a
> temp dir and then install'em in the virtualenv using sdist command .
Sorry `develop` command
> If using multiple slaves, I map that folder using e.g. SMB , ...
> That's quite much faster than other approaches ; but might not be
> useful under other circumstances (e.g. testrun.org) , and probably
> this hint won't help .
> PS: If I misunderstood your question please tell ;o)
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
> Featured article:
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
More information about the testing-in-python