Mailing-List: contact general-help@gump.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Gump code and data" <general@gump.apache.org>
Message-ID: <515742560.1131907103889.JavaMail.jira@ajax.apache.org>
Date: Sun, 13 Nov 2005 19:38:23 +0100 (CET)
From: "Leo Simons (JIRA)" <general@gump.apache.org>
To: general@gump.apache.org
Subject: [jira] Resolved: (GUMP-146) Need to run each build against a "fresh"
 CVS/SVN tree
In-Reply-To: <655469398.1121094610077.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GUMP-146?page=all ]
     
Leo Simons resolved GUMP-146:
-----------------------------

    Resolution: Fixed

Implemented in SVN revision 333089.

> Need to run each build against a "fresh" CVS/SVN tree
> -----------------------------------------------------
>
>          Key: GUMP-146
>          URL: http://issues.apache.org/jira/browse/GUMP-146
>      Project: Gump
>         Type: New Feature
>   Components: Python-based Gump
>     Versions: Gump3-alpha-5
>     Reporter: Leo Simons
>     Assignee: Leo Simons
>      Fix For: Gump3-alpha-5

>
> Gump2 has synchronisation functionality where we do a cvs/svn checkout of a project, then copy over that dir into the "work" area for the actual build. This ensures the build outputs of the last run don't influence the current one.
> Gump3 needs that functionality as well, probably best implemented by modifying the CvsUpdater and SvnUpdater plugins.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org