bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Martin <>
Subject Re: CI and virtualenv (Was: Re: [VOTE] Release Apache Bloodhound 0.1.0 (incubating) (RC1))
Date Fri, 03 Aug 2012 10:53:12 GMT

That is a good idea. I was thinking of possibly using buildbot to do 
that job as well. Of course, if a dist script is created it can always 
just call that instead so you idea probably provides the best basic 
solution. I believe you did mention one release process script from 
subversion so I will investigate that. Thanks.


My buildbot master.cfg needs a bit of redacting so I will try to fix 
that and commit it to the repository for others to suggest improvements 
by Monday or Tuesday. Anyway, I believe that this is a relevant snippet 
from my code:

    instdir = os.path.join("build", "installer")
    env = {'PATH': os.path.abspath("build/installer/bloodhound/bin") +
    envdir = 'bloodhound'
    pip = os.path.join(envdir, 'bin', 'pip')

    "--no-site-packages", envdir], workdir=instdir, name="install
    factory.addStep(ShellCommand(command=[pip, 'install', '-r',
    reqsfile], workdir=instdir, env=env, name="install packages"))
    factory.addStep(ShellCommand(command=[python, '',
    '-d', 'sqlite',
                                           '--admin-user=' + adminuser,
    '--admin-password=' + adminpassword], workdir=instdir, name="setup"))

steps after this were all tests of one sort or another followed by a 
removal of the bloodhound directory for a bit of cleanup just in case 
the buildslave is persistent.


On 08/03/2012 07:31 AM, Greg Stein wrote:
> I'd also recommend creating a "" script for assembling the
> tarball. For example, I queried if the wireframes should be
> distributed, and the answer was "no". That implies that assembling the
> tarball requires an "rm" step somewhere after the "svn export". It
> would be nice to script that, rather than following a list of manual
> steps.
> I believe that I've posted example types of scripts, but would
> be happy to repost if needed.
> Cheers,
> -g
> On Fri, Aug 3, 2012 at 12:26 AM, Olemis Lang <> wrote:
>> could you share your build script , please ?
>> On 8/1/12, Gary Martin <> wrote:
>>> On 02/08/12 01:57, Olemis Lang wrote:
>>>> On 8/1/12, Gary Martin <> wrote:
>>>>> On 30/07/12 12:48, Joachim Dreimann wrote:
>>>>>> Just for the record, I have downloaded reviewed the files to my
>>>>>> technical
>>>>>> ability.
>>>>>> +1 for the release from me.
>>>> I second that . The only thing I can mention is that even if manual
>>>> installation procedure works for me , on the other hand all the
>>>> attempts I made so as to install it from tarball in a Jenkins build
>>>> job have failed . This is mainly because :
>>>> 1. I'm not a proficient Jenkins user ...
>>>> 2. it seems there's an issue with virtualenv somewhere and ...
>>>> 3. I've not been able to dedicate any time to this task after the
>>>>       few initial experiments
>>> I appear to have been able to get things going with Buildbot with the
>>> virtualenv instructions, although I am not convinced that you can really
>>> activate the virtualenv in a buildstep. I didn't try this and instead
>>> resorted to a bit of trickery through which python binary was used after
>>> virtualenv creation.
>>> To be fair, there is no specific need to use virtualenv, as long as you
>>> have a fresh environment each time. My attempts so far have not been
>>> with throwaway VMs. Of course, I am sure that there will be other ways
>>> to isolate a python environment.
>>> Cheers,
>>>       Gary
>> --
>> Regards,
>> Olemis.
>> Blog ES:
>> Blog EN:
>> Featured article:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message