Re: Locks on the repository - Further information

> 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.

That seems like a bad plan to start with - what if the build fails in a way that
needs another developer's checkin to fix?

> 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.
>
> 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.

I think a better approach here would be to copy the head to a build branch
before starting the build. This allows development to continue on the trunk
without affecting your snapshot and lets you make as many changes as you
need to make the build complete. Then when the build is finished, copy it
to a tag with a name that you control for the release. That way nothing has
to stop and nothing is changed accidentally.

---
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org