|« The Evolving Worker - tools for a better day||How to run Pimki as a service under Windows with Cygwin - and how to back up its data »|
I've just started blogging about it and will likely blog more about it in the next few weeks: Rake gives you a tremendous power when it comes to automating tasks for any kind of applications, including DotNet applications. For those DotNet applications, I only delegate the compilation step to MsBuild. All the rest is handled through Rake itself, which may do the job itself and/or delegates stuff to other binaries (things like wget, winscp, unzip, gunzip, putty).
I usually setup a CruiseControl.Net instance when I start a DotNet project. When I started using Rake, I wanted to be able to call Rake from CruiseControl.Net.
Here's an extract of a working ccnet.config file calling Rake. You'll notice that the paths are absolute to ensure it doesn't rely on a PATH variable, which cause troubles when CCNet is running as a service.
You can call as many Rake tasks as you like on the same row. Properties (key=value) can be passed along, and retrieved later in the Rakefile using ENV['key'].
Bravo pour tes articles mais une question me turlupine depuis des années :-)
Pourquoi ecris-tu en Anglais alors que tu es aussi Français que moi et qu'il s'agit d'un site francophone
Cheers from NYC,
@Luke - thanks for your message! A "What I've done with Rake for my DotNet app" series is on my roadmap, stay tuned.
For my Rails applications and plugins, I'm using CruiseControl.rb. I'd probably use CCNet though to handle a Rails application for a customer already using CCNet or in need of more elaborate triggers.
If you don't know it already, have a look at cc.rb!
This post has 6 feedbacks awaiting moderation...