search

strongback / strongback-java

A library for FIRST Robotics Competition robots that makes it easier to write and test your robot code.
MIT License
41 stars 38 forks source link

Continuous integration / automated testing #5

Closed agausmann closed 9 years ago

agausmann commented 9 years ago

I am setting up a Jenkins CI server for my personal projects. Addition is painless since Jenkins supports Ant build scripts, and I think it would be a very useful tool for automated testing and release management.

The only downside is that the server has to authenticate as a user with admin rights in order to publish build statuses on GitHub. That means an existing owner/collaborator will have to generate an access token, or I will have to be promoted since I already have a token installed.

rhauch commented 9 years ago

+1 for automated CI -- it is a must have.

But IMO we don't want to rely upon the resources of any individual. Instead, I think we should use https://travis-ci.org, which is cloud-based, free for open source communities, far easier to configure than Jenkins, and works really well with GitHub. For example, it will annotate our GitHub repository with flags that state whether it builds successfully, and we can even add hooks so that any PRs are automatically built after the PR is created before someone has to look at it. And it already knows about Ant, and by default it will run ant test (tho we can change that if we need to).

The only reason I didn't register our repository already was that we need a build script, so as soon as issue #4 is resolved we can add Strongback to Travis to get automatic CI.

agausmann commented 9 years ago

Good idea. I don't have experience in Travis, but it seems it can do everything I was planning on doing. I agree; let's set it up once we have a build system.