At the moment I use SVN to manage java source code. Is there a solution out there whereby I can check in code and have the new code automatically compiled into a JAR file? Somehow the check in would need to trigger the compile process.
+5
A:
You need a continuous integration tool. Hudson would be a good choice (I've been using it the past year and it works really well)
Valentin Rocher
2010-01-13 12:43:17
+1
A:
You could do this with a CI server; the server can sit on another machine (the build server) and get the latest commit, build it, and compile it to a JAR. (Of course, this isn't really ideal, on large projects [due to lots of changes being submitted, and so on], but on personal things it should work to a reasonable degree).
Noon Silk
2010-01-13 12:43:20
CI is **especially** useful on large projects and any decent CI engine can deal with high number of commits. No, really, I don't get your point about large projects.
Pascal Thivent
2010-01-13 14:56:20
Pascal: Obviously, CI is useful, I was referring to the automatic building of every commit, (*that's* not useful, on large projects).
Noon Silk
2010-01-13 21:20:39
@silky : I don't agree with you. Having a build of every commit allows the devs to know exactly when the build breaks, and is not an extreme charge to the CI server.
Valentin Rocher
2010-02-23 16:49:39
@Valentin: Yes, but you don't want large projects building when they may take hours. It is typical to break your build process up, in this case.
Noon Silk
2010-02-24 07:29:02
A:
There are a number of continuous integration programs which do this very thing. Two I've used are Bamboo (commercial) and CruiseControl (open source). Bamboo is about 1000x easier to setup then CruiseControl, and really pays for itself after you've created a hundred build plans or so. With CruiseControl you will have killed yourself long before you get to your hundred build plan.
brianegge
2010-01-13 13:01:52