Source control woes

One of my Dev Services task this week was to investigate alternative source control systems to replace the aging CVS. Although the original plan was to move to SVN, it was decided to play around with a few distributed source control systems such as Git, Mercurial and Darcs.

The main metric used for the evaluation was how decent is the Eclipse plugin for the given system and as a playground I’ve used the CruiseMissile project straight from our CVS.

Unfortunately my report is pretty quick: none of the plugins are worth it so far. Although they are in constant development, they are still in a crude alpha state which would be risky for us to rely on. File diff and merging are poorly implemented, and some of the basic features we are used to, from the CVS plugin, are not available yet.

Thus, we are moving to SVN, at least for now. Apparently there are better tools for moving from SVN to some of these distributed systems, so that may still be an option in the future.

3 thoughts on “Source control woes”

  1. Hi,

    I’d be interested in the issues you had with MercurialEclipse, as this might improve the plug-in. What are the most important shortcomings in your point of view?

    Best regards,
    Bastian

  2. Hi Bastian,

    Paulo is on holiday, so I can try to respond in his absence.

    We use Eclipse for 99% of our version control “client” needs, (and that last 1% is mostly plumbing for scripts like Ant or Cruise Control.)

    We obviously use the standard “synchronize” behavior, but also we heavily use the visual diff editor and revision history. Paulo had a hard time using both the diff editor and revision history in the MercurialEclipse plugin.

    He also mentioned problems with some sporadic crashes. I am not sure if those were related to only the above Views or not.

    I hope that helps.

    Jason

  3. Thanks for the reply, Jason! As we have synchronization support, I’d of course like to know what you guys miss most – shouldn’t be too hard to add :-). Performance-wise, the beta release of today should be faster for synchronization.

    The visual diff editor is used by us as well – didn’t it work on your machines?

    Crashes… yuck. I don’t know of any issues right now, so if you got logs, feel free to send them to me :-).

Leave a Reply

Your email address will not be published. Required fields are marked *