Chad Woolley wrote: > This seems to make sense, only the builders should know about their > projects.
I assume you mean their plugins. Yeah, that makes sense; I was just surprised to see that the web app process has instances of all the builder plugins, but without their configuration loaded. It seems like if they're going to be there they ought to be configured. (Maybe the plugin instances are there as a side-effect of the plugin_loader code sitting at the bottom of project.rb?) > Maybe you can define a generic message (:deploy) that > triggers a build process to do something, similar to the build now > button. The builder process could then figure out how to 'deploy', > based on the individual project config (or do nothing, or do a default > command, if it is not configured). It's an option (with some really nasty monkey-patching to PollingScheduler), but it seems like a bad thing to give the builder process a second job. The deploy doesn't really belong in the web app process (in case it's long-running) but doesn't belong in the builder either. I think I'll dispense with configuring the deploy via cruise_config.rb and just make a normal Rails plugin for the time being. Thanks. -hume. _______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
