This post originated from an RSS feed registered with Java Buzz
by Marc Logemann.
Original Post: First impressions on TeamCity
Feed Title: Logemann Blog
Feed URL: http://feeds.feedburner.com/LogemannBlog
Feed Description: Marc Logemann's thoughts on java and other stuff
After using IntelliJ IDEA for several years now, i was excited if Jetbrains could deliver a server side product on the same level. To say it directly up front: Yes, i think so.
The toughest thing was not get TeamCity up and running... this was quite easy but to create a testing environment within our project which was "server ready". If we had done tests in the past (yes *if*, we are definitely bad in testing), we have done it on developer machines with the help of the IDE. I definitely wanted to use the ANT Runners inside TeamCity (TC) because we also have developers using Eclipse. So the option to use a IDEA Project runner was not the prefered one.
After modifying our ANT build file several times, we ended up with a quite good approach and i turned back to TC, getting into the config thingy. First i like the concept of distributed build agents. Even though i am using the agent on the same machine as TC Admin Server itself, it feels good to do to different (addtiional) platforms without any problems. Quite a big issues for product which should be able to run on various platforms.
You can manage the agents by triggering builds on VCS events or time shedule. We will go with a daily-approach first, because at this point we use it solely for code coverage benchmarking, but the next step would be to provide daily builds.
In the next weeks we will spend more time with TC and see how to tweak it for our internal needs. There is a lot to do in terms of end2end testing when it comes to databases and ORM and stuff. I am still unsure if we should use Derby and on the fly creation of production databases or link against a development database on a different server. And how well OpenJPA can handle Derby is also a big question mark. But hey, one step after another. I definitely will use the Spring Testing Framework which makes Spring bootstraping a lot easier in Test classes.