We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
I just finished watching the speech Linus Torvalds gave some days ago at Google, basically talking about GIT and Source Control Management.
He has really strong opinions but I think the video is really worth watching.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
C:\vb3>cm find marker
354 17/05/2007 10:51:35 excel dave
1665 18/05/2007 16:02:08 excel2 dave
C:\vb3>cm find revision where marker = 'excel' --format={item}
c:\vb3
c:\vb3\forest
c:\vb3\forest\TreeManifest.doc
...
C:\vb3>cm find "revision where changeset > 10 and branch = 'br:/main/clio' "
1586 17/05/2007 10:58:52 dir 11 dave c:\vb3#br:/main/clio#3
1597 17/05/2007 10:58:52 dir 11 dave c:\vb3\forest#br:/main/clio#0
...
C:\vb3>cm find revision where changeset between 10 and 13 --format="{changeset} {item}"
10 c:\vb3
10 c:\vb3\forest.removed.0.removed.0
12 c:\vb3\forest.removed.0\ForestWhitepaperES.doc
...
C:\vb3>cm find revision where marker = 'excel3' and not marker = 'excel2' --format={item}
c:\vb3\WindowsApplication1\Form1.cs
c:\vb3\WindowsApplication1\Form1.resx
...
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
SCRUM focuses on delivering software fast, on code instead documents, and on short release cycles, features which have become a part of our internal working methods since the beginning. CMMi asks for more strict processes, but at the end the key point is doing what you are suppposed to be doing according to your own definitions. Congratulations to the whole team!
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
$ cm add file00.c file01.c
$ cm ci file00.c file01.c
$ cm getfile file00.c#br:/main#LAST -file=filetocheck
$ cm getfile file01.c#br:/main#LAST -file=filetocheck2
public static void RunTest(string methodTestName, ExecuteTestDelegate test)
{
string testName = PNUnitServices.Get().GetTestName();
try
{
string[] testParams = PNUnitServices.Get().GetTestParams();
string wkbasepath = testParams[0];
string servername = testParams[1];
PNUnitServices.Get().WriteLine("The client should wait until the server starts");
PNUnitServices.Get().InitBarrier(Names.ServerBarrier);
PNUnitServices.Get().InitBarrier(Names.EndBarrier);
// would wait for the server to start
PNUnitServices.Get().EnterBarrier(Names.ServerBarrier);
// execute the test
test(testName, servername, wkbasepath);
// notify the end
PNUnitServices.Get().EnterBarrier(Names.EndBarrier);
CmdRunner.TerminateShell();
}
catch( Exception e )
{
PNUnitServices.Get().WriteLine(
string.Format("{0} {1} FAILED, exception {2}", methodTestName, testName, e.Message));
throw;
}
}
private void DoAddCheckInCheckOut(
string testName,
string servername,
string wkbasepath)
{
string wkpath = null;
try
{
string repname = "mainrep-" + testName + "-DoAddCheckInCheckOut";
wkpath = TestHelper.CreateRepAndWorkspaceWithSelector(
testName, servername, wkbasepath,
repname,
new SelectorTest (SelectorTypes.SELECTOR, new string[] {repname}));
// check out parent directory
CmdRunner.ExecuteCommand(
string.Format("cm co . -wks={0}", servername), wkpath);
// add a file
string filepath = Path.Combine(wkpath, FILE_NAME);
FSHelper.WriteFile(filepath, FILE_CONTENT);
CmdRunner.ExecuteCommand(
string.Format("cm add {0} -wks={1}", filepath, servername), wkpath);
// check in
CmdRunner.ExecuteCommand(
string.Format("cm ci {0} -wks={1}", filepath, servername), wkpath);
// check out
CmdRunner.ExecuteCommand(
string.Format("cm co {0} -wks={1}", filepath, servername), wkpath);
// check the file content
Assert.IsTrue(FSHelper.ReadFile(filepath) == FILE_CONTENT,
"The file {0} doesn't have the expected content", filepath);
// check in parent dir
CmdRunner.ExecuteCommand(string.Format("cm ci . -wks={0}", servername), wkpath);
}
finally
{
// clean up the workspace
if( wkpath != null )
FSHelper.DeleteDirectory(wkpath);
}
}
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
Here you can find a brief installation guide, to help you on installation process:
Client pre-install Requirements
Server pre-install Requirements
Eclipse pluing pre-install Requirements
Installation Steps
Configuration parameters
Server configuration parameters
Client configuration parameters
Post-installation Steps
If you chose to skip component setup during the installation, you can configure later both client and server through the ‘configureclient’ and ‘configureserver’ binaries, available under the installation directory.
The server can be managed with the script ‘plasticd’ (copied by the installer in /etc/init.d, and also in the install directory) supplying any of these arguments:
Usual Problems
If any problem should arise after the install, consider the following items:
The user who does the installation or anyone who wants to use Plastic SCM must have the following environment variables:
0 comentarios: