Re: Preventing Commits to a Branch
Jake Colman writes: > > Is there a way to prevent commits to be done to a specific branch? Once the > branch has been released we want to make sure it is not furthur modified. In > a releated manner, is there a way to prevent an assigned tag from being moved > or deleted from a specific revision? Look up the "commitinfo" and "taginfo" files in the manual. -Larry Jones These things just seem to happen. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Preventing Commits to a Branch
You may create a program to be called on every commit operation. Your program must analyze the file names, their revision numbers (the third part of revision number identifies the branch - the x in 1.1.x.1 identifies the branch x) and decide if the commit operation is legal or not. Use program exit code to tell cvs what to do - exit code 0 to allow commit operation and exit code > 0 to deny it. Read more about this on Cederqvist (CVS Manual - Appendix C), commitinfo administrative file Cheers, Xandao. > -Original Message- > From: Jake Colman [mailto:[EMAIL PROTECTED] > Sent: Friday, June 20, 2003 5:34 PM > To: [EMAIL PROTECTED] > Subject: Preventing Commits to a Branch > > > > Is there a way to prevent commits to be done to a specific > branch? Once the > branch has been released we want to make sure it is not > furthur modified. In > a releated manner, is there a way to prevent an assigned tag > from being moved > or deleted from a specific revision? > > TIA! > > -- > Jake Colman > > Principia Partners LLC Phone: (201) 209-2467 > Harborside Financial Center Fax: (201) 946-0320 > 902 Plaza Two E-mail: [EMAIL PROTECTED] > Jersey City, NJ 07311 www.principiapartners.com > > > ___ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs > ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Preventing Commits to a Branch
Alexandre Augusto Drummond Barroso <[EMAIL PROTECTED]> wrote: >> You may create a program to be called on every commit >> operation. Your program must analyze the file names, their >> revision numbers (the third part of revision number identifies >> the branch - the x in 1.1.x.1 identifies the branch x) and >> decide if the commit operation is legal or not. Use program >> exit code to tell cvs what to do - exit code 0 to allow commit >> operation and exit code > 0 to deny it. >> >> Read more about this on Cederqvist (CVS Manual - Appendix C), >> commitinfo administrative file The Cederqvist says: Much of the information about the specific commit request being made, including the destination branch, commit message, and command line options specified, is not available to the command. The args I see (with version 1.11.2) are: directory files. ie: /net/cvs/cvs/CVSROOT/cl_commit_check: /cvs/CVSROOT cl_commit_check How are you suggesting we find out the version number from this? >> >> Cheers, >> >> Xandao. >> >> > -Original Message- >> > From: Jake Colman [mailto:[EMAIL PROTECTED] >> > Sent: Friday, June 20, 2003 5:34 PM >> > To: [EMAIL PROTECTED] >> > Subject: Preventing Commits to a Branch >> > >> > >> > >> > Is there a way to prevent commits to be done to a specific >> > branch? Once the >> > branch has been released we want to make sure it is not >> > furthur modified. In >> > a releated manner, is there a way to prevent an assigned tag >> > from being moved >> > or deleted from a specific revision? >> > >> > TIA! >> > >> > -- >> > Jake Colman >> > >> > Principia Partners LLC Phone: (201) 209-2467 >> > Harborside Financial Center Fax: (201) 946-0320 >> > 902 Plaza Two E-mail: [EMAIL PROTECTED] >> > Jersey City, NJ 07311 www.principiapartners.com >> > >> > >> > ___ >> > Info-cvs mailing list >> > [EMAIL PROTECTED] >> > http://mail.gnu.org/mailman/listinfo/info-cvs >> > >> >> >> ___ >> Info-cvs mailing list >> [EMAIL PROTECTED] >> http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Preventing Commits to a Branch
Kevin Layer writes: > > The args I see (with version 1.11.2) are: directory files. ie: > > /net/cvs/cvs/CVSROOT/cl_commit_check: /cvs/CVSROOT cl_commit_check > > How are you suggesting we find out the version number from this? You can run "cvs -n status" (the -n causes it to ignore the lock that's in place for the in-progress commit). -Larry Jones I stand FIRM in my belief of what's right! I REFUSE to compromise my principles! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Preventing Commits to a Branch
--- Kevin Layer <[EMAIL PROTECTED]> wrote: > Alexandre Augusto Drummond Barroso <[EMAIL PROTECTED]> wrote: > > >> You may create a program to be called on every commit > >> operation. Your program must analyze the file names, their > >> revision numbers (the third part of revision number identifies > >> the branch - the x in 1.1.x.1 identifies the branch x) and > >> decide if the commit operation is legal or not. Use program > >> exit code to tell cvs what to do - exit code 0 to allow commit > >> operation and exit code > 0 to deny it. > >> > >> Read more about this on Cederqvist (CVS Manual - Appendix C), > >> commitinfo administrative file > > The Cederqvist says: > >Much of the information about the specific commit request being >made, including the destination branch, commit message, and command >line options specified, is not available to the command. > > The args I see (with version 1.11.2) are: directory files. ie: > > /net/cvs/cvs/CVSROOT/cl_commit_check: /cvs/CVSROOT cl_commit_check > > How are you suggesting we find out the version number from this? commitinfo trigger, parse the Entries file. Reject all commits from someone that updates/checkouts with branch number (to much work to figure out branch tag), require that all checkouts/updates, other that MAIN, be via branch tag. have trigger check each file's Entries file line. Not that difficult with a decent scripting language. We have branch control now with CVS that is dynamically configured by a config file. taginfo . defined a format for protected tags and have the script protect them from unauthorized users. To see what's info/files are available to use for a giving trigger type, add this trigger (for unix server) (note script might have issues, typed on the fly, but you should get the jist of it) #!/bin/perl print "ARGV = '@ARGV'\n\n"; @out=`env`; print "env = \n' @out'\n\n"; @out=`pwd`; chomp @out; print "PWD = '$out[0]'\n"; @out=`ls -Rla\n`; print "LS = \n' @out'\n"; exit 0; __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
