@@ -26,7 +26,7 @@ engine. Use it.
26
26
27
27
Buildbot
28
28
--------
29
- `Buildbot <http://buildbot.net/buildbot/docs/ current >`_ is a Python system to
29
+ `Buildbot <http://docs. buildbot.net/current/ >`_ is a Python system to
30
30
automate the compile/test cycle to validate code changes.
31
31
32
32
38
38
Tox
39
39
---
40
40
41
- `tox <https ://bitbucket. org/hpk42/tox >`_ is an automation tool providing
41
+ `tox <http ://tox.readthedocs. org/en/latest/ >`_ is an automation tool providing
42
42
packaging, testing and deployment of Python software right from the console or
43
43
CI server. It is a generic virtualenv management and test command line tool
44
44
which provides the following features:
@@ -53,7 +53,7 @@ which provides the following features:
53
53
54
54
Travis-CI
55
55
---------
56
- `Travis-CI <http ://travis-ci.org/ >`_ is a distributed CI server which builds tests
56
+ `Travis-CI <https ://travis-ci.org/ >`_ is a distributed CI server which builds tests
57
57
for open source projects for free. It provides multiple workers to run Python tests
58
58
on and seamlessly integrates with Github. You can even have it comment on your Pull
59
59
Requests whether this particular changeset breaks the build or not. So if you are
@@ -83,6 +83,6 @@ notifications, before and after steps and much more. The
83
83
`travis-ci docs <http://about.travis-ci.org/docs/ >`_ explain all of those and are very
84
84
thorough.
85
85
86
- In order to activate testing for your project, go to `the travis-ci site <http ://travis-ci.org/ >`_
86
+ In order to activate testing for your project, go to `the travis-ci site <https ://travis-ci.org/ >`_
87
87
and login with your Github account. Then activate your project in your profile settings and that's
88
- it. From now on, your project's tests will be run on every push to Github.
88
+ it. From now on, your project's tests will be run on every push to Github.
0 commit comments