cvs proxy suggestions

Here is the file pontis.bugid.verify mentioned earlier.
Sorry for the delay.
#!/bin/sh
#
# bugid.verify filename
#
# Verify that the log message contains a valid bugid
# on the first line.
#
# PONTIS SPECIFIC
# PONTIS SPECIFIC
# PONTIS SPECIFIC
# Change History
##################################################################################
# Allen R. Marshall, CS - 2003-12-29 - initiated
# Allen R. Marshall, CS - 2004-01-06 - updated to require formatted string

# and changed help comment
# Allen R. Marshall, CS - 2004-01-07 - updated help text for bad messages.
# Allen R. Marshall, CS - 2004-01-21 - allowed 1-3 digits of bug ID
# e.g. PON-1 is OK, PON-02 is OK, PON-002 is OK
##################################################################################
# 3 digits 009
if sed 1q < $1 | grep '^Bug\ ID:\ [ ]*PON-[0-9][0-9][0-9]*$' > /dev/null;
then
exit 0

# 2 digits 09
elif sed 1q < $1 | grep '^Bug\ ID:\ [ ]*PON-[0-9][0-9]*$' > /dev/null;
then
exit 0

# 1 digit 9
elif sed 1q < $1 | grep '^Bug\ ID:\ [ ]*PON-[0-9]*$' > /dev/null; then
exit 0

elif sed 1q < $1 | grep '^Bug\ ID:\ [ ]*none$' > /dev/null; then
# It is okay to allow commits with 'Bug ID: none',
# but do not put that text into the real log message.
# ARM - 2004-01-21 - let the message go in. All logging was getting
suppressed
# grep -v '^Bug\ ID:\ [ ]*none$' > $1.rewrite
# mv $1.rewrite $1
exit 0
else
echo "Commit message rejected - bad format,"
echo "No valid Pontis Bug ID was found on the first line of the
message!"
echo
"=========================================================================
"
echo "Format example:"
echo "Bug ID: PON-422 "
echo "or"
echo "Bug ID: none"
echo "and, additional useful, illuminating commit message text
echo "must follow....
echo
"=========================================================================
"
echo "Although you can enter > none < for the bug id, we implore you to
"
echo "please try to reference a specific Pontis bug in "
echo "JIRA bugtracker format e.g.Bug ID:PON-nnn or PON-422"
echo "whenever checking in a change in response to a known bug or "
echo "enhancement request."
echo "You can also embed any number of bug IDs in your commit text"
echo "like - This fix addresses the issues with bugs PON-422, PON-423,
PON-52"
echo "blah blah blah blah..."
echo
"=========================================================================
"
echo "Last updated: 01/07/2004 by ARM"
echo
"=========================================================================
"
exit 1
fi

RE: log detail.

I agree that the log contents should be economical but there are
definitely times during initial configuration of CVSProxy or a new CVS repo
when a user might want all the details including the specific cvs command
detail with command line arguments. Perhaps you might want to consider
some sort of granularity control to selectively suppress/allow different
logging levels.....

Thanks,Igor, for the responses. I have reviewed the article on PB
mentioned but I did not notice a specific patch requirement for SCC
support. Those message boxes are just a minor annoyance anyway.

I have a couple other questions/suggestions:

a) I use a commenting template with WinCVS so the comments follow a regular
format. The comment is validated using 'verifymsg' when the object(s) are
committed. Malformed comments will not check in (cvs commit). The
template looks like:

Bug ID: none
Condition:
Fix:
Comments:

It is accessed in the WinCVS commit dialog (WinCVS 1.3.13.2) by clicking
the Template button.

I happily fill in the template in WinCVS following the format and can
commit my revisions. A typical comment looks like:

Bug ID: PON-490
Condition: Architectural improvements, retrofit language support
Fix: Upgraded database abstraction layer module db_operations
Comments: blah blah blah blah etc.

This passes the verifymsg process.

If I enter the exact same comment in the comments dialog for CVSProxy, it
will fail to commit every time. If however I enter just 'Bug ID: none'
which is the only part of the template that is actually evaluated for
format , the commits will succeed from CVSProxy. I then have to use WinCVS
Admin to fix the log message, which is very inconvenient to say the least.

I have pasted in both VerifyMsg with its actual validation script
pontis.bugid.verify from my cvs repo and the template file for you.


>>> CUT
VERIFYMSG
# The "verifymsg" file is used to allow verification of logging
# information. It works best when a template (as specified in the
# rcsinfo file) is provided for the logging procedure. Given a
# template with locations for, a bug-id number, a list of people who
# reviewed the code before it can be checked in, and an external
# process to catalog the differences that were code reviewed, the
# following test can be applied to the code:
#
# Making sure that the entered bug-id number is correct.
# Validating that the code that was reviewed is indeed the code being
# checked in (using the bug-id number or a seperate review
# number to identify this particular code set.).
#
# If any of the above test failed, then the commit would be aborted.
#
# Actions such as mailing a copy of the report to each reviewer are
# better handled by an entry in the loginfo file.
#
# One thing that should be noted is the the ALL keyword is not
# supported. There can be only one entry that matches a given
# repository.
# PONTIS ENABLED FOR BUG MESSAGE VERIFICATION
# Allen R. Marshall, CS - 2003-12-29 created directive
#
# Allen R. Marshall, CS - 2004-03-18 - use symlink for repository...
^pontis /repository1/CVSROOT/support/pontis.bugid.verify

(I will have to send the script file later on)

The other odd thing is that when the commit fails for poorly formatted
message ( I assume ) I do not get the expected warning message that I have
embedded in pontis.bugid.verify...

SUGGESTION B

The use branch for checkout 'checkbox' doesn't seem to stick very well
between sessions. I have to go verify it every time I log in and it
unchecks itself during sessions too.

SUGGESTION C

The CVSPROXY DLL appears to stick in memory after Powerbuilder exits. When
I shutdown Windows, a warning message appears indicating this. Not sure
what that's about..

THANKS!

I have several observations having used the product for some time now:

(In the Powerbuilder 9 environment)

a) The log does not show the cvs update or cvs checkout commands that are
issued to obtain new/fresh objects. It should. In particular, it should
show that the desired BRANCH is in the arguments
b) The Get Latest Revision dialog comes up with a StopSign icon, like a
fatal error has happened, but it should be using an Exclamation Point!
instead, since it is just a confirmation dialog.
c) The Advanced button on the Get Latest REvision dialog does not do
anything, and also shows a fatal error stop sign icon even though the
button returns no error.
d) I am not seeing the cvs revision numbers in the Powerbuilder library
painter but I think that is Powerbuilder's fault.
e) Refresh of libraries is happening too often - how can I set this to a
longer interval or 'On Demand'?
f) All the checked out objects being managed by PushOK shows as 'Locally
Modified' to WinCVS, even though most have not been touched at all except
perhaps to do a 'GET'. This leads to annoyances doing straight WinCVS
checkouts to the same folders. Perhaps this was intentional, but unless an
object is actually 'touched' I don't think its cvs status should change to


Thanks!

(BTW: The message dialog window should read 'Please type your NEW message
below:')

:)