Recently created ideas in Beanstalk about Beanstalk

The dashboard shouldn't display days where no commits have been made. E.g. "yesterday" is displayed with the text "No activity on this day" -- it would be nicer if it just wasn't displayed at all.

It seems this could be a good feature for us but I need to understand it better...

First, we need logs/error messages why a deployment to FTP fails. I could not get it to work the first try and gave up for now because it doesn't tell me why the deployment fails.

Just as background, currently we svn update manually both our dev servers and the live server.

Whenever we deploy something to live, we create a new tag (as I would think is good practice). How does that tie in with the deployment feature?

I'd like the Activity Overview page to refresh periodically, perhaps with a lightweight poller to determine if any changes have been committed to the repository and a full-page refresh when its happened.

It's conventional style in a lot of projects to provide a summary of the commit as the first line of the commit message, and then follow it with a blank line and a more detailed description of the changes. This way, you can have long, detailed commit messages without having a giant chunk of text show up in the repo browser. Show only the first line in the repo browser, and then show the rest of the commit message when viewing the actual changeset.

I was wondering if there was a plan to integrate the beanstalk app with a jabber bot or IRC bot. I don't use campfire with my developers, but do use IRC and we all have Jabber JIDs - so integrating with either IRC or jabber would be awesome.

I'd love to be able to search though commit history either based on keywords. I spend a good amount of time figuring out what other team members did, and being able to search for concepts throughout the history of commits would be killer for me.

I don't know if you would want to have search terms applied to commit mesages, code content, or usernames, but there is definitely a chance for some interesting features here. Perhaps, instead of search, take advantage of tagging...that would work quite well with the Lighthouse integration.

This is no small task, but you could probably add some of this functionality just by tossing acts_as_ferret onto changeset models. (BTW, I'm assuming this is built in Rails and not .Net...I know Wildbit does both) This could definitely grind your server pretty hard, though.

We have integrated our account with Lighthouse and are always a little thrown off that beanstalk changes over to the next day several hours before our lighthouse account does.

I'm guessing that you are using GMT as the server time. If we could set the timezone for our account it would be very helpful.

There is a well known rails plugin to handle this - http://agilewebdevelopment.com/plugin...

-dave

Commit emails don't look as nice as svnnotify... We prefer our old svnnotify with -handler HTML:ColorDiff!

The subject of the mails contains also more information with svnnotify...

Could you add an integration that just adds an email address to a project for all commit notifications?

I love the lighthouse integration, but we have people in our group who don't have access to the repository or to lighthouse. They just like to see the general flow of things and we do that by sending out commit notifications to an email list.

If there were a way to add an email address to receive all commit notices that would be great.

Hi,

It would be nice if you have another payment option like Paypal. Because finding credit card every time for payment is not my thing. Too much to input. hehe..

This is a tiny little thing, but if the user has an account with ssl, maybe make the url in the Repository url box have https instead of http.

I noticed toggling between openid and username/password did not clear the contents of previous login method chosen. On one project I have two beanstalk accounts, one for myself and one for the deploy user. When trying to login using username/password for the deploy user, the openid field still had my openid in it and logged me in using that.

It would be nice if there were a way to grab the subversion URL of any arbitrary directory within the repository. At the moment (from what I can see) you only provide the URL on the overview screen for the repo.

Or is this already possible?

There is a high level of overlap in beanstalk (bs), basecamp (bc) and lighthouse (lh). Specifically projects (bs, bc, lh), users (bs, bc, lh), and milestones (bc, lh).

It would be fantastic to sync the projects from basecamp to beanstalk and to lighthouse, and do the same for milestones. This would also go for users. So, considering that basecamp would be the center of operations (used by project managers) we could do the following:
1) Create a new project in basecamp. Go to beanstalk and flag that project to be "synced". This would auto-create the repository and auto-create a lighthouse project. It would also auto-create all of the appropriate user accounts.

2) Sync users between Basecamp and beanstalk and lighthouse. If I manage users in lighthouse, it should manage users in beanstalk and lighthouse.

3) Sync Milestones between Basecamp and Lighthouse.

I realize that basecamp has a weaker API that does not allow for many things to be remotely created. However, it does allow most things to be exported. And lighthouse does a great job with their API allowing you to do nearly anything remotely.

The only draw-back is that there is no way to attach events to basecamp so that when a new milestone, project, user is created that beanstalk can know about it and act accordingly.

Another point of integration with Basecamp would be to integrate with Basecamp milestones.

You could say that a commit completes a milestone, or say that a new tag/branch in the SVN completes a milestone.

This milestone would then be counted as completed in Basecamp.

There is built in integration with Lighthouse for bugs/issues, could the same integration be considered for Google Code bugs/issues?

I would happily go with Lighthouse, except they don't have public projects allowed for free accounts.

I'd love to put that 'this commit fixes bug #111', and have it automatically close that bug in the Google Code issues section.