[EMAIL PROTECTED] wrote: > Hi everyone, > I was wondering if anyone is aware of any canned scripts or > tools that are > available that will improve our code migration processes. > > We have 3 tags that we use for our builds 1) TEST 2) QA 3)PROD > > Any developer can tag code as "TEST", but project managers > need to request > that code gets tagged as QA and/or PROD. [...]
> One last thing! I get multiple tags at a time for QA and > PROD builds. > For example, I may get BUGZILLA_123, BUGZILLA_124, BUGZILLA_156, ... > Dependent upon what order I do the tagging, I can actually "demote" a > revision of a file. > For example, example.jsp version 1.23 may have tag BUGZILLA_156 > and version 1.24 has BUGZILLA_124. > I need to prevent the case where I am applying a QA or PROD > tag to a file > where the tagging operation would cause the QA or PROD tag to > fall upon a > revision number that is lower than the current pre-tagged > state. Make > sense? > > I would very much appreciate a pointers on how to resolve > these holes in > our curent process. The taginfo script (http://www.cvshome.org/docs/manual/cvs-1.11.15/cvs_18.html#SEC175) allows you to hook into tag operations, and your script can check whatever rules you want set up. Check the contrib directory of the release. Someone may have contributed something that you can use or adapt. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
