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=21110>.
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=21110

Gump performs builds on stale code

           Summary: Gump performs builds on stale code
           Product: Gump
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Java/XSLT
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Gump is using out of date stuff:

Note: At time of writting these links were useful, but since they go 
to "latest" their value may change over time.

        -----------------------------------------------------------------------
        http://cvs.apache.org/builds/gump/latest/cvs_krysalis-version.html

        cvs -z3 -d
:pserver:[EMAIL PROTECTED]:/cvsroot/metamorphosis
update -P -d -A krysalis-version

        cvs [update aborted]: recv() from server 
cvs.metamorphosis.sourceforge.net:
EOF
        cvs server: Updating krysalis-version
                ...
        /home/rubys/bin/timeout: timed out
        cvs [update aborted]: received termination signal
        -----------------------------------------------------------------------

SourceForge have knobbled their CVS server against such accesses (in the
name of making developer lives easier) and much as this is an SF.net user
woe, two things:

1) Even if/when gump detects that CVS fails it only seems to mark the CVS
index in red, it doesn't mark the main build dashboard in red. As such, such
failures can go unnoticed.

        http://cvs.apache.org/builds/gump/latest/cvs_index.html krysalis-
version =
FAILED
        http://cvs.apache.org/builds/gump/latest/index.html krysalis-version =
SUCCESS.

2) The reason the build dashboard isn't in red is that Gump doesn't (it
seems to me) clean out it's CVS area each time, so it has a "stale" copy of
the code with which to "update" the build area and with which to build.

FWIIW:

3) Gump doesn't seem to clean out it's work area each time, which can be
confusing when profiles change and projects get renamed or go away.

This is one of the things I mean to log in the bug tracker, now Sam's
created it.

BTW: I suspect a fix might be in adding to the gump.sh script that Sam
wrote, and Nick Chalko and I built upon. Not elegant (yet another language
in the mix, and no PC version) but easiest...

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to