Fog Creek Software
Discussion Board




Checkin manager

Does anyone know of tool that teams of developers can use to let one another know the status of a project under source control? Something that sits in the system tray and allows you to easily check whether it's safe to get latest or not, what the current version is, who was the last person to check in etc.

Adrian
Thursday, May 27, 2004

I am not sure if anything is out there on the market but it sounds like a cool app to build....

Gen'xer
Thursday, May 27, 2004

Surely your source-control app should tell you this.

It should always be "safe to get", as nobody should check in something that is unsafe.

Steve Jones (UK)
Thursday, May 27, 2004

Every build on your mainline should be "safe" to get the latest (to the extent that the engineers would be able to ascertain this in the first place without going through a full QA process).  If people want to check in under potentially unsafe conditions, use a separate branch; keep the mainline clean and buildable at all times.

You should already know who the last person to check in was, without any effort.  If you don't, get a real version control system (like Perforce, which does automatic emailing).

Writing an app to get around a bad versioning process is just a band-aid for the bad process.  Get a real version control system and make sure your developers are trained in how to use it properly.

BadgerBadgerBadger
Thursday, May 27, 2004

But don't choose Continuus, it's a dog.

Steve Jones (UK)
Thursday, May 27, 2004

Tinderbox?

Joel Spolsky
Fog Creek Software
Thursday, May 27, 2004

Anthill or CruiseControl

http://www.urbancode.com/projects/anthill/default.jsp
http://cruisecontrol.sourceforge.net/

Oren Miller
Thursday, May 27, 2004

Thanks to Joel and Oren for the suggestions. Much appreciated.

Adrian
Thursday, May 27, 2004

If you just want a little tool, I've used VSS Monitor at http://www.vssconnect.com/VssMon.htm . It sits in your system tray and gives you a popup when a file you are monitoring in visual sourcesafe becomes available, but I think it only works for Microsoft VSS. Hope this helps.

Josh

Josh
Thursday, May 27, 2004

"Tinderbox"

Joel, you just gave me flashbacks of my old junior high Dungeons & Dragons days.........

:-)

Gen'xer
Thursday, May 27, 2004

You might also consider using a revision control system that supports atomic commits. Without this feature, even with the most diligent of developers, you'll still run into the kinds of race conditions that make the checkin manager necessary in the first place.

Derek
Thursday, May 27, 2004

> Surely your source-control app should tell you this.

Yes.

> It should always be "safe to get", as nobody should check in something that is unsafe

There is always the possibility that you get the code in the middle of someone else checking in a bunch of files, get some of the changes and not the rest.


Friday, May 28, 2004

"There is always the possibility that you get the code in the middle of someone else checking in a bunch of files, get some of the changes and not the rest."

This only happens in obsolete systems like VSS which are based on submitting individual files rather than entire changelists.  Using changelists prevents this problem from happening.  Get Perforce.

BadgerBadgerBadger
Friday, May 28, 2004

*  Recent Topics

*  Fog Creek Home