[cvsnt] Re: storing lock files on cvs

[glenn opdycke-hansen]

The application/system deploys code to one or more remote hosts.
The code for the application is stored in cvsnt.  I do not have access
to a database.  Since multiple people can be deploying from different
PCs at the same time, there was a chance that the same application
could be deployed to the same host.
The goals were to be able to see what deploys were active and to
provide a mechanism that would prevent multiple concurrent deploys.

I think that storing the lock files in cvsnt could work.  I am looking
for some feedback.
The bulk of the system is written in Ant.  Reading a db from Ant is
possible, just not something that I have experience with.

--glenn

On 4/13/06, Glen Starrett <glen.starrett at march-hare.com> wrote:
> glenn opdycke-hansen wrote:
> > I have an application is stored on cvsnt.  I want to show active requests in
> > the application as files stored in a cvs module.
> >
> > Is this a reasonable design?  When a request is started a file is created in
> > the locks module and it needs to be added/committed.
> > To check if a lock exists, the locks module needs to be updated.
> > To remove a lock the file needs to be removed/committed.
>
> What is the overall purpose of your system?  The way I read this, it
> sounds like you're trying to use CVSNT for something that a database
> might better serve.  It's difficult to assess without a full view of the
> system, and this isn't a good forum for that.
>
> --
> Glen Starrett
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
>