diff options
| author | holger krekel <holger@merlinux.eu> | 2011-10-13 08:29:01 +0200 |
|---|---|---|
| committer | holger krekel <holger@merlinux.eu> | 2011-10-13 08:29:01 +0200 |
| commit | e1f18c9ebb906f6a1ec91e62581e7a50dc2f10f5 (patch) | |
| tree | dae3ceb54bf0fd9b0ce960b705326c8c25d16a56 | |
| parent | 648d5421e987c74d772e19c143253e1ae9cae0eb (diff) | |
| download | tox-e1f18c9ebb906f6a1ec91e62581e7a50dc2f10f5.tar.gz | |
fix issue16 - mention that Jenkins Python plugin needs to be installed
| -rw-r--r-- | doc/example/jenkins.txt | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/example/jenkins.txt b/doc/example/jenkins.txt index a2bdb6b..f092c22 100644 --- a/doc/example/jenkins.txt +++ b/doc/example/jenkins.txt @@ -11,6 +11,7 @@ default Python installation on each Jenkins slave, you can easily create a Jenkins multi-configuration job that will drive your tox runs from the CI-server side, using these steps: +* install the Python plugin for Jenkins under "manage jenkins" * create a "multi-configuration" job, give it a name of your choice * configure your repository so that Jenkins can pull it * (optional) configure multiple nodes so that tox-runs are performed @@ -35,7 +36,7 @@ for example with ``py.test`` it is done like this: See a real-life example in action with the `pytest Jenkins job`_ -.. _`pytest Jenkins job`: http://jenkins.testrun.org/view/pytest/job/pytest/ +.. _`pytest Jenkins job`: http://hudson.testrun.org/view/pytest/job/pytest/ **zero-installation** for slaves ------------------------------------------------------------- |