Set up CI

[guykisel]

You can pretty easily set up a job that will automatically run tests against every commit and every pull request. I can help with this if there's interest.

For example, see https://travis-ci.org/guykisel/robotframework-faker

[pekkaklarck]

We actually already have CI set up at http://robot.radiaatto.ri.fi but it hasn't been updated yet to track GitHub repository. It runs tests on Python 2.5-2.7, Jython 2.5 and IronPython 2.7, both on Linux and Windows. If we get same platform support elsewhere, I'd be happy to swtich. Otherwise we just need to reconfigure old service and also add a note about it to README and/or other docs. Definitely a must for 2.8.6.

[guykisel]

Oh, cool, I never saw this. Jenkins has the capability to build GitHub pull requests, too, though it requires a plugin. https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin

[guykisel]

I think Travis is capable of running IronPython and Jython if configured properly, but if you already have Jenkins set up then I don't see a good reason to switch.

Example Travis config with IronPython: https://github.com/earthreader/libearth/blob/master/.travis.yml

[guykisel]

Turns out Travis phased out support for Python 2.5, so Jython testing isn't really possible. I suggest sticking with the existing Jenkins setup.

[jussimalinen]

I just updated the jobs to poll now the github project. So that should work.

I will next take a look at getting the automatic pullrequest testing to work. (Or semiautomatic, we need to manually check the pull request before accepting it to run on the CI machine of course.)

[jussimalinen]

Now there is an almost automatic build for pull requests. We still need figure where to document the ci. Probably to contribution instructions.

[pekkaklarck]

I agree that CONTRIBUTING.rst is the best place to write information about CI, but the problem is that we don't yet have it. I think this is what we should do:

• Document CI here. Its location is already mentioned above, but we should explain how running PRs works.
• Add an issue about writing contribution guidelines and refer this issue from there.