I think the benefits section is fine. I did not find it confusing when I was eva...
I think the benefits section is fine. I did not find it confusing when I was evaluating Hudson. As the Benefits section suggests, you might not want to run all unit tests before committing, if you are fairly confident the code is OK and the tests take a long time to run. Out of the box Hudson does not prevent you from committing if the code does not compile or does not pass unit tests. You could create that kind of setup if you wanted. For example, I downloaded all the necessary programmes to do that on search on torrents http://www.picktorrent.comHudson just polls your repository and then builds and reports. And it's so easy to get set up. The Maven integration is good. That's why I use Hudson.
Comments (1)
Jan 19
Anonymous says:
I think the benefits section is fine. I did not find it confusing when I was eva...I think the benefits section is fine. I did not find it confusing when I was evaluating Hudson. As the Benefits section suggests, you might not want to run all unit tests before committing, if you are fairly confident the code is OK and the tests take a long time to run. Out of the box Hudson does not prevent you from committing if the code does not compile or does not pass unit tests. You could create that kind of setup if you wanted. For example, I downloaded all the necessary programmes to do that on search on torrents http://www.picktorrent.comHudson just polls your repository and then builds and reports. And it's so easy to get set up. The Maven integration is good. That's why I use Hudson.
Add Comment