Re: Getting the high revision number

On Tuesday 01 August 2006 15:07, Reedick, Andrew wrote:
> Because he said:
> Right now, I'm using a php script to call
> 'svn info --non-interative -R' on the repository url

Oh, I missed that.

> Which sounds like he's getting the build number from the
> repository after the code has already been checked out.

Or he wants to find out what to put in the checkout command.
But then he could just go without specifying a number.

> In my experience, you should know what revision you want to build
> _before_ you create the working copy...

True.

> An environment (QA, UAT, whatever) has build 1234. Can you tell
> me where build 1234 came from, given this repository:

That's why I said it could be more helpful to include branch information.
Which then is also a URL only, so I guess you're right.

> I'm approaching this from the CM side. If dev wants fuzzy dev
> builds (for speed or continuous integration,) then that's ok. However,
> when the time comes for a formal build and deployment to QA, fuzzy is
> way too expensive and painful.

Point taken.

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 22:36:54 2006