July 2017
Beginner to intermediate
340 pages
7h 43m
English
Content preview from Python Microservices Development
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
Start your free trial
Continuous Integration
Tox can automate every step you are doing when you change something in your project: running tests on various Python interpreters, verifying coverage and PEP 8 conformance, building documentation, and so on.
But running all the checks on every change can be time and resource consuming, in particular, if you support several interpreters.
A Continuous Integration (CI) system solves this issue by taking care of this work every time something changes in your project.
Pushing your project in a shared repository under a Distributed Version Control System (DVCS) like Git or Mercurial, on a server will let you trigger a CI every time someone pushes a change on the server.
If you work on an open source software, and don't want ...