On Wed, May 7, 2008 at 6:07 AM, nicholas a. evans <[EMAIL PROTECTED]> wrote: > > If we still use those hashes for build labels, we'll need to order > > builds by mtime of a build directory and display abbreviated build > > labels instead of full ones. Or we need to generate our own build > > numbers. > Personally, I'd strongly prefer generated build numbers
In the latest checkin, we are abbreviating global changeset ids (long random hex strings) for both Git and Mercurial to the first five characters. It turns out that both Git and Mercurial allow you to specify changesets in this way, so it is a meaningful label, problem solved. 5 characters sounds like a short string. We thought about what happens if two changesets have the same first five characters. First of all, 16^5 is just above a million, so chances of that actually happening are not that big. And then, consequences are not that serious - it will just create a new build with the .1 suffix, like it was a rebuild. We are also sorting builds by mtime of the build directory. Whether this is a performance concern remains to be seen by testing on a project with large number of builds. Bottom line: Mercurial and Git support available from the master repository (previously known as trunk) passes some tests and looks usable by now. If you need it desperately enough to deal with unreleased software, please try it out and see what happens. -- Alexey Verkhovsky CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] RubyWorks [http://rubyworks.thoughtworks.com] _______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
