On Jan 5, 2008 12:42 PM, John D. Hume <[EMAIL PROTECTED]> wrote:
> This morning I sat down to try to start writing a cruise plugin that
> allows you to deploy ('cap deploy' or something similar) a revision
> that has built successfully by clicking a link or button on the
> builds/show page. (I.e., something that satisfies
> http://jira.public.thoughtworks.org/browse/CCRB-55.)
>
> Since I want to be able to configure the command to run in each
> project's cruise_config.rb, I looked into making it a builder plugin
> (even though those normally do all their work in the builder processes
> rather than the web app). I was happy to find the builder plugins are
> created in the web app process, but then disappointed to find out the
> project configuration isn't loaded in that process, only in the
> builders.
This seems to make sense, only the builders should know about their
projects. 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).
Kind of vague, sorry, I didn't review the source. Would that work?
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
