[Twisted-Python] Travis-CI integration work

Hi, I just want to let you know that we are almost done with the work of integrating Travis-CI with Twisted GitHub PRs. The ticket is here https://twistedmatrix.com/trac/ticket/7229 If you have time, please take a look at the current work and suggest any changes or provide any feedback. The goal of this ticket is to have an initial set of tests executed for a patch, on behalf on non-Twisted commiters. In this way, I hope that contributors would be able to get a faster feedback regarding the quality of their patch. This should also reduce the work required to review a branch, as commiters will no longer have to merge and send to buildbot each new revision submitted by a contributor. Cheers, -- Adi Roiban

Travis-CI integration for Twisted has reached a milestone! Travis has been set up and is currently in use for Twisted. For pull requests submitted against Twisted: https://github.com/twisted/twisted/pulls the Travis service will build it, and report status in the pull request itself. The build status of pull requests is also available on the Travis site: https://travis-ci.org/twisted/twisted/pull_requests This is how it works: - The *.travis.yml* file checked into the Twisted source tree gives the Travis service the commands that should be executed. - In .travis.yml, we make use of *tox-travis* ( https://pypi.python.org/pypi/tox-travis ). - tox-travis looks tells Travis to execute tox, using the *[tox:travis]* section in the *tox.ini* file checked into the Twisted source tree. This is how Travis executes the Twisted tests Thanks to Adi for taking my initial patch for this, finishing it off, and doing the initial Travis setup. Thanks to cyli for doing the final review of the patch and for committing it to trunk. -- Craig

Travis-CI integration for Twisted has reached a milestone! Travis has been set up and is currently in use for Twisted. For pull requests submitted against Twisted: https://github.com/twisted/twisted/pulls the Travis service will build it, and report status in the pull request itself. The build status of pull requests is also available on the Travis site: https://travis-ci.org/twisted/twisted/pull_requests This is how it works: - The *.travis.yml* file checked into the Twisted source tree gives the Travis service the commands that should be executed. - In .travis.yml, we make use of *tox-travis* ( https://pypi.python.org/pypi/tox-travis ). - tox-travis looks tells Travis to execute tox, using the *[tox:travis]* section in the *tox.ini* file checked into the Twisted source tree. This is how Travis executes the Twisted tests Thanks to Adi for taking my initial patch for this, finishing it off, and doing the initial Travis setup. Thanks to cyli for doing the final review of the patch and for committing it to trunk. -- Craig
participants (4)
-
Adi Roiban
-
Craig Rodrigues
-
Glyph
-
Jason J. W. Williams