Ayende @ Rahien

Hi!
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:

ayende@ayende.com

+972 52-548-6969

, @ Q c

Posts: 6,123 | Comments: 45,465

filter by tags archive

A visual look at RavenDB velocity

time to read 1 min | 172 words

We recently added a very small feature to our build server, generating tags on the repository for every successful build. This has the surprising effect of giving us a really nice way of looking into something that I always wanted, the rate of change across pushes to production.

The way we work in Hibernating Rhinos, every single push to the remote repository is a viable product, and it becomes a a publicly available build. The problem is that in git there isn’t really a way to track pushes, so it was quite hard to figure out after the fact the scope of change of each build without looking at the individual commits.

With the new tags, we have a much easier time. I mean, just take a look:

image

You can see pretty rapid velocity here, with new goodies that come abroad.


Comments

Fatal

I see no commits for 6/25/2011. What a bunch of slackers!

Roy
Roy

There's quite a lot of time between build 392 and 393, what kind of build rules do you use? Not per commit apparently, but is there a special reason for that?

Ayende Rahien

Roy, We have a build per push, commits are local to each dev env, push are globally visible.

Roy
Roy

Ah, of course. That makes sense. Having a tag like this will also make the version number a lot more friendly to the end user, compared to showing the short commit hash.

Joe
Joe

Completely irrelevant, but the check-in comments are interesting -- is it a cultural or technical background thing that makes some people comment in the past tense (Fixed, added, etc) vs the current tense?

Comment preview

Comments have been closed on this topic.

FUTURE POSTS

  1. RavenDB 3.5 whirl wind tour: You want all the data, you can’t handle all the data - 3 days from now
  2. The design of RavenDB 4.0: Making Lucene reliable - 4 days from now
  3. RavenDB 3.5 whirl wind tour: I’ll find who is taking my I/O bandwidth and they SHALL pay - 5 days from now
  4. The design of RavenDB 4.0: Physically segregating collections - 6 days from now
  5. RavenDB 3.5 Whirlwind tour: I need to be free to explore my data - 7 days from now

And 13 more posts are pending...

There are posts all the way to May 30, 2016

RECENT SERIES

  1. RavenDB 3.5 whirl wind tour (14):
    29 Apr 2016 - A large cluster goes into a bar and order N^2 drinks
  2. The design of RavenDB 4.0 (12):
    28 Apr 2016 - The implications of the blittable format
  3. Tasks for the new comer (2):
    15 Apr 2016 - Quartz.NET with RavenDB
  4. Code through the looking glass (5):
    18 Mar 2016 - And a linear search to rule them
  5. Find the bug (8):
    29 Feb 2016 - When you can't rely on your own identity
View all series

RECENT COMMENTS

Syndication

Main feed Feed Stats
Comments feed   Comments Feed Stats