@@ -26,7 +26,7 @@ engine. Use it.
2626
2727Buildbot
2828--------
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
3030automate the compile/test cycle to validate code changes.
3131
3232
3838Tox
3939---
4040
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
4242packaging, testing and deployment of Python software right from the console or
4343CI server. It is a generic virtualenv management and test command line tool
4444which provides the following features:
@@ -53,7 +53,7 @@ which provides the following features:
5353
5454Travis-CI
5555---------
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
5757for open source projects for free. It provides multiple workers to run Python tests
5858on and seamlessly integrates with Github. You can even have it comment on your Pull
5959Requests 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
8383`travis-ci docs <http://about.travis-ci.org/docs/ >`_ explain all of those and are very
8484thorough.
8585
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/ >`_
8787and 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