You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by "Leo Simons (JIRA)" <ge...@gump.apache.org> on 2005/07/11 17:10:10 UTC
[jira] Created: (GUMP-146) Need to run each build against a "fresh" CVS/SVN tree
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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
[jira] Resolved: (GUMP-146) Need to run each build against a "fresh" CVS/SVN tree
Posted by "Leo Simons (JIRA)" <ge...@gump.apache.org>.
[ 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
[jira] Assigned: (GUMP-146) Need to run each build against a "fresh" CVS/SVN tree
Posted by "Leo Simons (JIRA)" <ge...@gump.apache.org>.
[ http://issues.apache.org/jira/browse/GUMP-146?page=all ]
Leo Simons reassigned GUMP-146:
-------------------------------
Assign To: Adam Jack
> 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: Adam Jack
> 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
[jira] Assigned: (GUMP-146) Need to run each build against a "fresh" CVS/SVN tree
Posted by "Leo Simons (JIRA)" <ge...@gump.apache.org>.
[ http://issues.apache.org/jira/browse/GUMP-146?page=all ]
Leo Simons reassigned GUMP-146:
-------------------------------
Assign To: Leo Simons (was: Adam Jack)
> 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