Hello guys,
Can someone please review the job I created for running the lava-tool unit tests?
https://ci.linaro.org/jenkins/job/lava-tool/
The CI build script is very simple: virtualenv ci-build-venv ci-build-venv/bin/python ./setup.py test
My first try did not go well, since virtualenv is not installed:
https://ci.linaro.org/jenkins/job/lava-tool/1/console
What's the appropriate way to make sure virtualenv is installed? I presume I cannot add `apt-get install -q -y python-virtualenv` in the top of the build script ...
On 22 May 2013 19:16, Antonio Terceiro antonio.terceiro@linaro.org wrote:
Hello guys,
Can someone please review the job I created for running the lava-tool unit tests?
https://ci.linaro.org/jenkins/job/lava-tool/
The CI build script is very simple: virtualenv ci-build-venv ci-build-venv/bin/python ./setup.py test
My first try did not go well, since virtualenv is not installed:
https://ci.linaro.org/jenkins/job/lava-tool/1/console
What's the appropriate way to make sure virtualenv is installed? I presume I cannot add `apt-get install -q -y python-virtualenv` in the top of the build script ...
First, you should restrict the job on a slave. Otherwise, it will use master, which isn't set up for builds. Then we need to pre-install your build dependencies on the custom AMI.
Anyway, sorting out on IRC now :)
linaro-validation@lists.linaro.org