One of the global option for cvs is the -s VARIABLE=VALUE. Look at page 155
in the Open Source Development with CVS manual. So, you could do something
like:
cvs -s BUGID=mybugid commit -m "I just fixed mybugid" file.c
If your loginfo file contains a line:
myproj /usr/local/bin/foo.pl ${=BUGID}
Then foo.pl script is invoked with 'mybugid' as an argument. Armed with
this, you could easily add a script to associate bugids with specific
checkins. Then the "meta-data" would be associated with the specific
revisions accessable to any greedy build miester.
Hope this helps,
Matt Berney
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 08, 2000 11:14 AM
To: [EMAIL PROTECTED]
Subject: Track the changes between the builds???
Ok, here is the deal. I am a buildmaster in my company. I am trying
to track the BugID numbers that were submitted into the current build
since the last build. The way i build, consists of updating all the
projects, tagging all the files with current-date-year-time and then
extracting for the build...i just implemented the rcsinfo templates
that allow developers to enter bugID at every commit...basically all
i need to do is to run log -rtag: command where tag=the tag of the
last build, redirect the output to a temp file and query for all the
different bugID numbers...I was wondering if there is a different way
of doing it??? or what is the more convinient point of the build
process to call the log??? I was looking at taginfo...can the list
be produced automatically while i am tagging the next build? Any
ideas or comments are greatly appreciate??? and other ways of going
around the task???
all the help is greatly appreciated,
-Julia
