[TIP] Weird problem with Jenkins: ShiningPanda plugin and Tox, but not tox on its own...
chris at simplistix.co.uk
Sun Jul 1 13:37:23 PDT 2012
On 01/07/2012 20:20, Olivier Mansion wrote:
> Have you changed the UNIX user that starts the Jenkins instance?
Not on the problematic Linux slave, but even on the Mac slave it seems
> And if you try to delete the .tox folder, does this fix the issue on the
> next build?
In all the machines, I completely deleted the shiningpanda folder and
the workspaces for all the tox jobs, eg:
jenkins at server2:~/slave$ rm -rf shiningpanda/ workspace/*-tox
...but still the same problem:
Is this maybe a change in the Tox package? How can I force the
ShiningPanda tox builder to use tox 1.3 instead of 1.4 to check?
Simplistix - Content Management, Batch Processing & Python Consulting
More information about the testing-in-python