开发者

Is there a practical limit on number of tags in SVN?

Here's a similar question for SourceSafe. We have a single SVN repository storing sources of numerous projects. Among those projects something like 25 are built every day each by a dedicated daily build. Once daily build starts it tags the sources with its own name (something like "Build of Pr开发者_如何学Gooject N version X.Y.Z", Z increases with every successive build of project N).

Are there any practical limitations in SVN we can run into with such scheme? Is there a practical limit on the number of tags in SVN repository?


On a practical basis, I would personally find it very annoying if I tried to view the list of tags in my repository browser to find the Project_v2.0 tag, but I had to scroll through 2000 daily build tags to see it. So I would suggest keeping these in a separate subdirectory: /tags/daily/build_0001


No, tags are very cheap in SVN since they are just a named revision.


Is there a practical limit on the number of tags in SVN repository?

I can imagine that mere browsing so many tags becomes slow after a few years of 25 daily tags, but you could overcome that by saving them hierarchically. Also, I wouldn't put them under tags, or at least not directly, lest they clutter the the folder and make it hard to find releases and such.

Otherwise I'm not aware of a practical limit. Tagging, at its heart, is making a lazy copy of a subtree and AFAIK, internally, each checked in revision basically is a lazy copy of the one before, so SVN uses that operation for every checkin. I'd seriously doubt that there's a limit you can reach.


I don't believe so. But what's the point of making a new tag every time you do a daily build? If you needed to you could just pull the sources by date...

0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜