Thanks a lot Paul and Andy...will you stick around?
Originally posted by Ilja Preuss:
That same developer today can't even imagine how other teams can work without a CI server...
Actually, for some time now, we are using a homegrown software to show the build state that supports not just the two states "success" and "failure", but also "failure noticed", "fix in progress" and "fix committed".
Resource dependency of Junit tests:[/b] the issue of junit tests that I can run locally but not on the CI machine
Another interesting first reaction to Cruise Control was that one of our core developers installed an email filter so that he wasn't any longer "pestered" by all those emails telling him that a build failed...
Developers committing code that breaks the build?
Happening from time to time. That's one of the things that make me wonder whether a manual CI process might work better.
Another thing that is rather annoying is that CVS commits aren't atomic, so that every now and then we have a build failure simply because of an inconsistent checkout.
What are your thoughts, if any, about BDD versus TDD?
The only thing I'm not familiar with there is what you mean by building system components separately. Could you elaborate on that?
I'd advise to make sure that you don't measure something just because it's easy to measure. Think hard about how you will use the information you will get. Having the process produce information that isn't acted upon has a high risk of reducing the perceived significance of the whole process.
Others, though, voice the opinion that ideally, CI isn't done using a tool, but manually.
What is your point of view in the book?
The property file contains things like the database url, the
mail server details...
These things vary in each environment.
The problem is that as our project grows large, build times are hovering around 20 minutes. Is that abnormal for a CI process?...what do you see as an acceptable maximum for the CI build time?
We were using cruise control but it seems like it was slowing down the server. Then we installed Pulse, but it has the same problem. Now we are thinking of Hudson.
Do you folks use any better?
Any recommendations from Author/s?
Any good about Hudson?
could they use the book as a �check-list� to see if the CI is used "correctly" or if there's something missing?
The team I work in uses continuous integration, but only within a system. We run an automated unit test suite every time code is checked in. However, a lot of issues arise in the interfaces between systems, i.e. database access, remote updates, interface changes etc.
Is this something that CI could be applied to? That is CI appropriate for inter-system as well as intra-system use? If so any tips on how go about putting tests (test harnesses?) in place?
I am new to Java. What is the best process to get an Application executable to run on a client PC. We are using Ant where I work is this the best step to take.
Also, when you build an app in Eclipse why is it you can save a program to a .exe instead of have using javac.