Sync with tfs on CodePlex

[wvd_vegt]

Hi

 

I'm trying to sync a CodePlex project of mine under TFS with a local PlasticScM repo. I cannot get the correct cm.exe syntax (help is a bit short).

 

 

I got to

 

cm sync br:/main tfs https:\\tfs.codeplex.com:443/tfs/TFS04/ghostbuster --user=snd\<name>_cp --pwd=<pass>

 

inside a workspace but it does not work.

 

I'm getting errors like:

 

Error: The settings you've introduced don't match with the stored ones for branch/repo /main. Stored are: lq

 

Any suggestions?

 

regards

[calbzam]

Hi,

 

You need to indicate Collection and Project this way:

http://stackoverflow.com/questions/16576313/using-plasticscm-or-any-dvcs-client-to-connect-to-tfs/16589120#16589120

 

At this link, you can check an example.

 

Regards,

Carlos

[wvd_vegt]

Hi

 

The sample is for a local team foundation service (I already found it but it did not work as is and contains no explaination).

 

I tried:  

cm sync br:/main tfs https://tfs.codeplex.com:443/tfs/TFS04\\DefaultCollection 
$/GhostBuster --user=snd\<user>_cp --pwd=<pass> 

and got: 

 
Error: Team Foundation services are not 
available from server https://tfs.codeplex.com/tfs/TFS04//DefaultCollection.Technical 
information (for administrator):  Page not found.

Btw notice the // are reversed in the answer.

 

When I try: 

C:\temp\GhostBuster>cm sync br:/main tfs https://tfs.codeplex.com:443/tfs\\TFS04 
$/GhostBuster --user=snd\<user>_cp --pwd=<pass>

I get more results but still an error:

 
Latest cset on foreign SCM: 98950
 
 
- 18 changesets to pull- 0 
changesets to push
Counting changesets to 
pull...Importing... | 1/18Sync status saved: plastic cset 1 -> tfs commit 
49993Importing... / 2/18Error: TF10122: The path 
'$/GhostBuster/$/ghostbuster/Ghostbuster.sln' contains a '$' at the beginning of 
a pathcomponent. Remove the '$' and try again.

Removing the $ (after first recreating the repo and workspace) I get:

 

Error: There is no working folder mapping 
for C:\GhostBuster.

 

If I do not recreate the repo and workspace I get the original error I posted:

 

Error: The settings you've introduced don't match with the stored ones 
for branch/repo /main. Stored are: lq

regards
 

[wvd_vegt]

Hi

 

Got the correct syntax after much experimenting:

cm sync /main@GhostBuster@lenovo:8087 tfs https://tfs.codeplex.com:443/tfs/TFS04 
$/ghostbuster --user=snd\<user>_cp --pwd=<pass>

where:

• /main is the PlasticSCM branch to sync.
• GhostBuster is the name of the PlasticSCM repository to sync.
• lenovo:8087 is the name of the local PlasticSCM server and port number.
• TFS04 is the name of the collection (you can get it from the Connect link on the Source Code tab, It varies per project).
• ghostbuster is the project name (you can get it from the Connect link on the Source Code tab, it is case sensitive).
• snd\<user>_cp is the username,<user> is the normal login name for codeplex, snd\ is a domain prefix and _cp a username suffix.
• <pass> is the codeplex password that belongs to <user>.

regards

[calbzam]

Hi,

 

Thank you very much for your feedback!

 

Regards,

Carlos

[wvd_vegt]

Hi Carlos,

 

No problem, you guys make a great product so whatever I can do in return...

 

I also posted above explaination on stackoverflow.

 

Btw are there any plans to add Mercurial sync as well?

 

regards

[calbzam]

Hi, 

 

At the moment a Hg sync is not in the roadmap. Thanks for your words!!

 

Regards,

Carlos 

[Gerard Murphy]

I stumbled across this old post whilst Googling for information about Plastic / TFS interoperation.

 

Regarding Hg <-> Plastic sync, I have successfully used the hg-git extension for Hg to sync my Hg repository to Git (on GitHub) and the the Git <-> Plastic sync to bring those changes into Plastic - works well, even with Mercurial named branches in the mix.

 

You can go the other direction as well.

 

The only thing that isn't supported is exporting Plastic labels back to Git and thus to Hg (although this may have been implemented in the meantime).

 

These days I don't bother with Hg any more, but I've done this often enough in the past to be confident that it works well.

[calbzam]

Hi @Gerard,

 

Thanks a lot for your feedback

 

Regards,

Carlos