gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leo Simons (JIRA)" <>
Subject [jira] Closed: (GUMP-1) Gump performs builds on stale code
Date Sun, 27 Mar 2005 20:31:21 GMT
     [ ]
Leo Simons closed GUMP-1:

     Assign To:     (was: Gump Development Team)
    Resolution: Won't Fix

The java version of gump is not maintained anymore and won't be maintained anymore. Sorry!

> Gump performs builds on stale code
> ----------------------------------
>          Key: GUMP-1
>          URL:
>      Project: Gump
>         Type: Bug
>   Components: Java/XSLT
>     Versions: unspecified
>  Environment: Operating System: Other
> Platform: Other
>     Reporter: Adam Jack

> 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.
> 	-----------------------------------------------------------------------
> 	cvs -z3 -d
> update -P -d -A krysalis-version
> 	cvs [update aborted]: recv() from server 
> 	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 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.
> krysalis-
> version =
> krysalis-version =
> 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.
> 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 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...

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message