web front end input

[Craig Jolicoeur]

Hello all Cerberus users,

I'm at the point where I'm seriously considering starting/finishing
work on a web front-end for Cerberus.

This will be a separate gem that can be installed in addition to
Cerberus to view build output via a browser. I don't want to include
it into the main Cerberus gem, because I want Cerberus to remain as
lightweight as possible.

Most likely it will just be a simple Sinatra/Rack application that
displays the current build status and previous build information.

I'd like input from current users who might be interested in something
like this, what kind of data you'd like to see on a web front-end.
What kind of data points and info would be valuable.

Also, if anyone has good UI and/or design skills, I'd love help with
some mockups of what this simple app should look like.

Thanks

- Craig

[Mike Gunderloy]

I'd also love to see the web front end provide API hooks for GitHub and CodaSet to trigger builds. I've got some very rough code for this hooked up on one of my servers I could probably find time to contribute.

Mike

[Craig Jolicoeur]

Yeah, providing API endpoints to trigger builds instead of just
showing stats is a good idea.

If you've done any legwork already, feel free to send me a link to any
code you'd care to share if you think it could jumpstart some of it.

> --
> You received this message because you are subscribed to the Google Groups "Cerberus" group.
> To post to this group, send email to cerbe...@googlegroups.com.
> To unsubscribe from this group, send email to cerberusci+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/cerberusci?hl=en.
>
>

[Paul Hinze]

Craig Jolicoeur <cpjol...@gmail.com> on 2010-03-17 at 15:26:

> I'm at the point where I'm seriously considering starting/finishing
> work on a web front-end for Cerberus.

I'm late to the party, but wanted to send a big +1 and an offer of help on any
aspect of developing this feature. Probably the biggest thing missing in my
current group's CI setup is "easily accessible _current_ build status", and a
web status page would solve that problem.

I like the idea of something uber-lightweight like Camping. I think we could
even consider just generating static HTML to be pushed and served to a location
of the user's choosing (there are downsides to this setup, but I think it's
worth at least putting on a list of possibilities).

Craig: have you gotten a chance to arrange any bytes on this yet? If so, is
there a branch you're willing to share? If not, what should our first steps
be?

Looking forward to building a killer feature! ;)

Paul

[Craig Jolicoeur]

I haven't started any coding on this yet. Ive actually been down in
Florida for the past few weeks on vacation with my family and will
probably start work on the web stuff in earnest when I get back next
week.

static HTML isn't a bad idea. I hadn't thought about it before, but
it's definitely a possibility and would be the easiest for users to
get up and running quickly. As you mentioned, there are drawbacks with
that approach where build info/history isn't stored in some sort of DB
or file.

Camping, Sinatra, static, etc... they all are options. Let's discuss
pros/cons of each and choose one and run with it.

My personal main goals would be a clean UI, and something that is
*very* easy to configure and get running on both an internal and
external web server.