Using same build id for multiple build servers

[tjruska]

We have 6 build servers, each running CCNet 1.4.1, and many builds use the same build id for multiple projects and\or repositories. I am questioning this use. Will\can there be contention using the same id when multiple builds are trying to fire at the same time? What would you recommend as best practice. Each repository have it's own unique build id? Or is this a mute point in the way Vault handles connections behind the scenes?

Tom

[jeremy_sg]

Do you mean the same build number, or the same build user login name? I'm going to assume the same build user login name, and answer that question, since it's easier. Yes, you can use the same build user login from multiple computers at the same time. The server separates user requests based on session id, so there will be no contention in the server.

[tjruska]

You guessed correctly! Same build user login id. But when you say server, is that the web server hosting the vault web service or SQL Server? I buy the no contention on the web server but what about SQL Server? Is there a possibility of any locking or is it a "dirty" read?

Tom

[jeremy_sg]

There is the possibility of locking, but for the most part, the operations that CC.Net does (refresh, get, label) are read only.