[Cruisecontrolrb-users] Adding Deploy Button to GUI

[Mike Papper]

Hello, has anyone tried to add a "deploy" button. This would look like
the "build now" but be positioned for every successful build (on the
main projects page where it displays the status of the last 5 builds
per project). It would then run capistrano with that tag.

Something we've been thinking about so I thought I would check and see
if someone has done this already.

Also, I was going to put a new action into one of the controllers but
maybe the "plugins" is some way of extending CruiseControl in a more
modular way? Any insight on this?

Mike
_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecont...@rubyforge.org
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

[Chad Woolley]

On Mon, Jul 26, 2010 at 7:08 PM, Mike Papper <bodar...@gmail.com> wrote:
> Hello, has anyone tried to add a "deploy" button. This would look like the
> "build now" but be positioned for every successful build (on the main
> projects page where it displays the status of the last 5 builds per
> project). It would then run capistrano with that tag.

Your email made me have an idea: There should be a deploy button, but
with a configurable webhook which passes the build number. That would
allow anyone to hook any cross-platform deploy hook, and wouldn't
require anything to be run on the cruise server (or added to the
codebase to do so).

[Donovan Bray]

I have a project that has a cap task to do the deploy, we use it just to have a button to deploy to our test server. You can set it to trigger on a successful build of a different project if you like.

[Brian Guthrie]

On Tue, Jul 27, 2010 at 8:17 AM, Chad Woolley <thewoo...@gmail.com> wrote:
> On Mon, Jul 26, 2010 at 7:08 PM, Mike Papper <bodar...@gmail.com> wrote:
>> Hello, has anyone tried to add a "deploy" button. This would look like the
>> "build now" but be positioned for every successful build (on the main
>> projects page where it displays the status of the last 5 builds per
>> project). It would then run capistrano with that tag.
>
> Your email made me have an idea:  There should be a deploy button, but
> with a configurable webhook which passes the build number.  That would
> allow anyone to hook any cross-platform deploy hook, and wouldn't
> require anything to be run on the cruise server (or added to the
> codebase to do so).

I've thought about adding a deploy button before; I like the webhooks
idea. (That'd also be a nice mechanism for handling chained builds
across multiple servers.)

I admit, though, that I'm not sure how the details would work here. Is
the idea that CCRB would POST to the given URL on deploy, and
whoever's running on the other end of that is expected to know how to
deploy the app? That seems like more trouble than just asking CCRB to
run a Cap/Rake task for you.

Brian