Thanks a lot for doing this. I suppose that https://github.com/sympy/sympy/pull/1239 can be closed now.
One suggestion is to install the Chrome or Firefox browser extension at http://about.travis-ci.org/docs/user/browser-extensions/, which will place the build status on every github page. Aaron Meurer On Jun 20, 2012, at 11:58 PM, "Ondřej Čertík" <[email protected]> wrote: > Hi, > > With this pull request (https://github.com/sympy/sympy/pull/1363) the > master branch in the official repository is now > automatically tested by Travis CI. The link to the web interface (also > in the README.rst in the Tests section): > > http://travis-ci.org/sympy/sympy > > The way it works is that there is '.travis.yml' file in the repository > and travis-ci.org is connected with sympy/sympy at github via github > hooks. > Every time a commit is made to the master branch (the only branch in > the official repository) a test run is triggered at travis-ci.org. > As far as I understand, almost anything can be done, as specified in > .travis.yml. For now, we just test Python 2.5, 2.6, 2.7 and 3.2 > and I first install sympy using "python setup.py install" and then > test it. That way, we also test that setup.py is correct. > However I think currently only tests are run, not doctests nor > documentation tests. Improvements are welcome (see below > how you can easily contribute and test it). > > Now the cool part: if you login to travis-ci.org with your own github > account, go to profile and flip a switch at the sympy repository, > then everytime you push *any* branch to your own github, it will be > automatically tested by Travis CI. So in particular, the testing > starts even before you manage to send a pull request. :) Just make > sure that you fork from the current master, so that > '.travis.yml' is in your branch. > > > In order to improve the testing, just study the Travis CI > documentation, then modify .travis.yml, push to your own github and > see if > it works or not. Then debug it by simply adding new commits. Once you > nail it down and things work, create a nice patch > and send a pull request. > > Travis CI also seems to allow testing of pull requests directly (for > people who don't have it setup --- even though it is really > trivial, see above): > > http://about.travis-ci.org/blog/announcing-pull-request-support/ > > But so far it is not enabled for our repository. As far as sympy-bot > goes, we'll simply continue using it, because it has > more features at the moment. We will see how it goes, if Travis CI can > do everything that we need, we can switch to > it later. > > Ondrej > > P.S. sympy-bot is currently broken: > https://github.com/sympy/sympy-bot/issues/110 > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sympy?hl=en. > -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
