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
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
