views:

132

answers:

0

What is the best way to setup perforce version control for the latest fitnesse distributions?
We have our fitnesse files under perforce version control, but manually checking out prior to each update is a bit of a pain.

Since the 20090214 release of Fitnesse, CM integration is included or more precisely plugins for version control systems can be built, as per:
http://fitnesse.org/FitNesse.UserGuide.SourceCodeControl

The SVN and git hub plugins are included with the fitnesse distribution.
I found the following Perforce CM system, which would seem to be what I need:
http://code.google.com/p/perforcecmsystem/

Seems like the above may have already been integrated into the fitnesse distribution based on:
http://github.com/unclebob/perforcecmsystem/tree/master If this is now built in, I need some further pointers on how to enable it.
If not may need to rebuild this source against the lastest distribution, which is a little more work since we are a .NET shop.

There is this alternate Fitnesse plugin for perforce version control, but it doesn't seems to follow the recommended CmSystem protocol. http://www.qaautomation.net/?p=14

We are testing a .NET project where we use the fit runner 1.8. I would like to get perforce integration working with the most up to date fitnesse distribution, but so far no luck with the 20090818 release.