gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 21652] New: - Gump does not detect cvs update failure due to renamed projects
Date Wed, 16 Jul 2003 12:54:26 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21652>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21652

Gump does not detect cvs update failure due to renamed projects

           Summary: Gump does not detect cvs update failure due to renamed
                    projects
           Product: Gump
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Java/XSLT
        AssignedTo: gump@jakarta.apache.org
        ReportedBy: michael.davey@coderage.org


The update script does not detect when cvs fails to update due to the
project being renamed.  As a result, cvs_index.html shows a "SUCCESS" status. 
This can currently be seen with the Apache James project:

cvs -z3 -d :ext:rubys@cvs.apache.org:/home/cvs update -P -d -A jakarta-james cvs
server: Updating jakarta-james cvs server: cannot open directory
/home/cvs/jakarta-james: No such file or directory cvs server: skipping
directory jakarta-james

http://cvs.apache.org/builds/gump/latest/cvs_index.html
http://cvs.apache.org/builds/gump/latest/cvs_jakarta-james.html

Perhaps a new status of "SKIPPED" could be introduced.  Either way, the current
implementation can cause changes to go un-noticed for some time.

Mime
View raw message