Mayank Gupta wrote:
> Hi,
>
> The reason is following:
>
> When I run the build, it takes around 30 minutes. In the build
> process I first do the checkout of source code, and then perform the
> build operations in sequence. My last build operation is a checkin in
> which I checkin some of the files created by the build process.
>
> To explain it further:
> Before starting the build, subversion head number is 800.
> Now I run the build and finally checkin few files and head number
> becomes 801. We consider 801 as the build release number.
>
> But if somebody else comes in between and checks in his source code,
> he will occupy 801 and I will get 802 (802 will be the release) and
> thus he will corrupt the whole build process because 802 does not
> have the exact release files.
Make a build branch from revision 800, and build and check back in *that*.
When you're done, you need to merge your changes back in.
No one else should be active in each other's branches in this kind of setup.
> So I want to solve this problem by locking the repository for the
> build time. I can add repository lock/unlock steps in my build
> process.
>
> With Regards,
> Mayank
That seems workable, but not ideal.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 28 12:30:18 2006