Notification with Campfire

[Jason Meridth]

Any examples with using campfire for notifications?

I'm assuming that I just edit the appname.yml file and instead of:

mail:
recipients: ma...@mail.com

I do

campfire:
username: username
password: password
subdomain: test
room: development

Right? I'm totally guessing.

[Craig Jolicoeur]

The Campfire publisher probably could stand to be updated. Let me
know if it works for you because I had a report last month that it
wasn't working, but the user never followed up with me again.

The campfire config is as follows. I believe most config examples can
be seen in your main config file ( ~/.cerberus/config.yml )

# campfire:
# url: http://someemail:pass...@cerberustool.campfirenow.com/room/51660

[Jason Meridth]

wow. I missed the examples in the base config.yml completely. Thanks
Craig.

I'll let you know about campfire.

Thanks for the quick responses.
--
Jason Meridth
jason.lostechies.com

[Craig Jolicoeur]

Jason

Just wondering how you made out with Campfire in Cerberus?

It work fine or did you run into problems?

- Craig

[Jason Meridth]

Craig,
I've bit had a chance to touch it again. I will tonight and give you
an update tomorrow

--------------
Jason Meridth

Sent from my phone. Please excuse typos and missing/extra characters.

On May 13, 2009, at 8:03 PM, Craig Jolicoeur <cpjol...@gmail.com>
wrote:

[Jason Meridth]

I was able to get the campfire notifier working. The only catch was
that I had to use the id of the room and not the name (string). That
took a little to figure out. Even when your example showed in the
error.log file.

Just a heads-up.

Thanks guys.

Now it's up to our team. This tool or another.

I am very tempted to help upgrade your docs, if that is cool. fork
and update. :)

On May 13, 8:03 pm, Craig Jolicoeur <cpjolico...@gmail.com> wrote:
> Jason
>
> Just wondering how you made out with Campfire in Cerberus?
>
> It work fine or did you run into problems?
>
> - Craig
>

[Craig Jolicoeur]

Oh man, I'd love some help updating the docs.

I've slowly been making notes here and there locally but haven't taken
the time to do a proper update online.

Any help you'd like to contribute would be much appreciated.

Thanks for the input thus far.

- Craig

[Niklas Koponen]

To help you in decision making I can tell our teams experiences.

I was responsible for building the ci environment. We use java (maven, wicket, spring). The project is built up of multiple modules. The modules contain unit tests and integration tests. Everything is run with maven.

We tried Continuum and Cruise Control. For some reason I could not grasp the complexity of those tools. I guess I'm simple in that way.

With Cerberus everything is visible, easily configurable and you can make modifications easily. If there is some documentation missing, the source code is quite easy to read.

If you have some ruby experience in your team and want a simple, versatile and robust "build running tool" then Cerberus is a great choice.

I certainly am glad that we have Cerberus running in our ci-environment that is easily configurable with a few yml files.

-Niklas

[Craig Jolicoeur]

Excellent news, so glad to hear it.

Everything you described are exactly the types of things we tried to
focus on when developing Cerberus.

I'm glad you found the easy configurability and lightweight footprint
to be exactly what you needed.

Thanks so much. Feedback like this is always encouraging.

btw, I do still have those two latest patches you submitted. I've got
them locally, just need to package them up and push out a new gem
release.

- Craig