Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

So who uses cruise control?

 
Dominic Clarke
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, I have a couple of problems with cruise control.

1. We currently have it set up to provide continuous integration on our project. However, the machine on which it is running does not have any jsp server software on it (I wasn't responsible for setting it up). Is it recommended to have this on it (I'm thinking along the lines of Tomcat here)? Is the only advantage being able to continuously monitor the build process through a browser? (currently we are sent out mails on success or failure of the build)

2. The error reporting only specifies a line in Build.xml as to what the problem is. Those unfamiliar with cruise control (artists and suchlike) aren't given much indication as to why the build is failing. Is there a way of actually reporting the specific step that the build broke down on?

Sorry for putting this stuff in here, but there's no message boards on the cruise control site.......


Thanks
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Dominic Clarke:
1. We currently have it set up to provide continuous integration on our project. However, the machine on which it is running does not have any jsp server software on it (I wasn't responsible for setting it up). Is it recommended to have this on it (I'm thinking along the lines of Tomcat here)? Is the only advantage being able to continuously monitor the build process through a browser? (currently we are sent out mails on success or failure of the build)


The webserver doesn't need to run on the same machine as the build loop - it only needs access to the logs folder.

The "only" advantage is to be able to see the state of the build (and previous builds) through a web browser, yes.


2. The error reporting only specifies a line in Build.xml as to what the problem is. Those unfamiliar with cruise control (artists and suchlike) aren't given much indication as to why the build is failing. Is there a way of actually reporting the specific step that the build broke down on?


I'm not sure I understand your question. Could you please provide an example of what kind of info you'd like to have?


Sorry for putting this stuff in here, but there's no message boards on the cruise control site.......


What about http://cruisecontrol.sourceforge.net/contact.html ?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic