Pieper: /* Key Investigators */

2008-06-27T12:48:44Z

Key Investigators

Pieper: New page: {| |Project Week Main Page ]] |} NOTOC ===Key Investigators=== * Sebastien Barre * Steve Pieper * Bi...

2008-06-23T11:46:50Z

New page: {| |thumb|320px|Return to [[2008_Summer_Project_Week|Project Week Main Page ]] |} __NOTOC__ ===Key Investigators=== * Sebastien Barre * Steve Pieper * Bi...

New page

{|
|[[Image:ProjectWeek-2008.png|thumb|320px|Return to [[2008_Summer_Project_Week|Project Week Main Page]] ]]
|}

__NOTOC__

===Key Investigators===
* Sebastien Barre
* Steve Pieper
* Bill Hoffmann
* Will Schroeder
* Jim Miller

<div style="margin: 20px;">

<div style="width: 27%; float: left; padding-right: 3%;">

<h1>Objective</h1>
To discuss options for supporting access to CVS repositories for people behind firewalls (includes corporate, overseas, hotels, etc).
</div>

<div style="width: 27%; float: left; padding-right: 3%;">

<h1>Approach, Plan</h1>

The current approach is based on the [http://slicer.spl.harvard.edu/slicerWiki/index.php/Slicer3-lib-mirror Slicer3-lib-mirror repository] which contains a full CVS checkout of a particular state of a toolkit checked into an SVN repository (see link for details).

Updating the SVN repository is currently done manually leading to the versions getting out of sync. A nightly or continuous update is possible, but unless done carefully could lead to a overwhelming of the SVN repository.

Options to consider:
* review current cvs to svn conversion scripts. Downside is that these take several hours to run for a large repository because they covert all history. When last checked weren't these also reported to require some manual intervention for some cases? (SP)
* write an automated version of the current approach which deletes the old versions completely (to save on database size).
* other options?

</div>

<div style="width: 40%; float: left;">

<h1>Progress</h1>

The current approach is successfully used by the experimental [http://slicer.spl.harvard.edu/slicerWiki/index.php/Slicer3:getbuildtest getbuildtest2.tcl] build script.

</div>

<br style="clear: both;" />

</div>

===References===

* [http://www.python.org www.python.org]

← Older revision		Revision as of 12:48, 27 June 2008
Line 42:		Line 42:

	The current approach is successfully used by the experimental [http://slicer.spl.harvard.edu/slicerWiki/index.php/Slicer3:getbuildtest getbuildtest2.tcl] build script.		The current approach is successfully used by the experimental [http://slicer.spl.harvard.edu/slicerWiki/index.php/Slicer3:getbuildtest getbuildtest2.tcl] build script.
		+
		+	This week we discussed options and decided that there is now ideal solution, but making a nightly export of cvs-based repositories into an svn mirror will work for the majority of cases. Kitware will set up a cron job to implement this functionality for CMake, ITK, VTK, and KWWidgets.

	</div>		</div>

2008 Summer Project Week:CVS SVN Synchronization - Revision history

Pieper: /* Key Investigators */

Pieper: New page: {| |Project Week Main Page ]] |} __NOTOC__ ===Key Investigators=== * Sebastien Barre * Steve Pieper * Bi...

Pieper: New page: {| |Project Week Main Page ]] |} NOTOC ===Key Investigators=== * Sebastien Barre * Steve Pieper * Bi...