Uploaded image for project: 'Gump'
  1. Gump
  2. GUMP-1

Gump performs builds on stale code

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Resolution: Won't Fix
    • None
    • None
    • Java-based Gump
    • None
    • Operating System: Other
      Platform: Other
    • 21110

    Description

      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:anonymous@cvs.metamorphosis.sourceforge.net:/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...

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            ajack@trysybase.com Adam Jack
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment