Re: Getting the high revision number

On Tuesday 01 August 2006 13:53, Reedick, Andrew wrote:
> a) You scare my inner CM child. The repository revision number(s) and
> the code/workspace revision number(s) are not guaranteed to be the
> same, so your build number is random.

Why random?
The working copy revision number is what he has checked out, which is what
he will use as build number and as code to build from.
If the working copy has no local modifications, that number is exactly
what he needs.
If he checks out a fresh working copy, he's fine as well.

> First, get the HEAD revision number of the project root using
> "svn info url/project_root".

Why not use svnversion, maybe in combination with a regex to just get one
of the numbers?

> You will probably want to make the build area readonly
> to everyone but the build owner.

Most compilers I know of want to create object files....

Also, if the build is automated, there should always be only one build
job.

> The build number should be: url + rev_num. A revision number
> by itself is useless if you have multiple projects, releases, branches,
> etc. in a repository.

Even if you do, the revision number can be fine if you say it's for the
foo product because you will always know the root of the foo project.

One could include tags or branch names, though, even if only for marketing
purposes ("beta 2").

> If you are building from a workset, then you can use 'svn info
> root_dir_of_workspace' to get the revision number. However, this
> assumes that the entire workspace is on the same rev number and isn't a
> mixed revision workspace.

Which is somewhat unlikely, but that's what svnversion is for.

Cheers,

Robert

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 1 21:17:05 2006