Geek Answers Handbook

Should CruiseControl.NET be used to handle tasks not related to the build source?

Perhaps a strange question. We have several simple utilities written internally that need to be run on an automated basis. This is not job creation. Just things like running SendOutHourlyEmailAlarms.exe , KeepFoldersInSynch.exe , etc. Usually I set these tasks as simple scheduled tasks / AT commands (or a Windows service if more detailed control is required for planning), but an employee set a number of these tasks as build projects on CruiseControl. NET I asked him why he installed them in such a way, and his answer was that executions (and their logs, return values, excluded exceptions) were tracked and recorded and that this information was accessible through an organized interface on the build server website. I could not argue with that.

But it has a smell that I cannot identify. Is this the correct use of CruiseControl.NET? If not, what is the danger? Even if this may be consistent with the bill, are there any other products more suitable for this type?

+6
source share
3 answers

We have all kinds of tasks that are not related to the assembly, for the same reason as your colleague, I want one place to look at all and all the tasks that I need to run.

Some examples of our CC.NET projects:

  • FTP Settings for Remote QA

  • Creating source code documentation

  • Create a virtual machine with installers installed for QA in the morning

  • Installer Archiving

Almost everything that I need to do manually, more than once, becomes a project. IMHO is much better than the planned task for another reason. Our configuration files are in the original management, so we have 1 place to configure. We do not need to register on multiple servers and make adjustments or wonder which server did this.

+6
source share

I think your colleague made a good argument. If these tasks are related to the development process, then placing them in CruesControl.Net as a project seems acceptable. However, I would use the line to use the development server to start production processes. Although it is true that “if the only tool you have is a hammer, you tend to see every problem as a nail”, this does not mean that the hammer is not able to solve many problems!

+2
source share

Just because the tool is designed to solve a specific problem does not mean that it will not have equal opportunities in solving such problems outside the area originally provided by the creator of the tool. If CruiseControl.NET solves these problems well, then this is an absolutely suitable tool to use.

+1
source share

More articles:


All Articles