leebrooks0 Posted June 26, 2011 Report Share Posted June 26, 2011 Will the upgrade from version 3 to version 4 be seamless when version 4 is released> Thanks Link to comment Share on other sites More sharing options...
miller Posted June 27, 2011 Report Share Posted June 27, 2011 In the BETA releases we will not have compatibility. When we GA the 4.0 we will probably work on the migration mechanism from 3.0 to 4.0, this what is on the table at at this stage. cheers, Miller Link to comment Share on other sites More sharing options...
hampsterx Posted November 8, 2011 Report Share Posted November 8, 2011 At present is there any way you can push a version 3 repository into a version 4 one or would you have to create a new repository from an existing working folder for example? Link to comment Share on other sites More sharing options...
manu Posted November 8, 2011 Report Share Posted November 8, 2011 Hi hampsterx, yes, you can use the fast-export command in 3.0 and create an import package file, then you just have to use the fast-import command in 4.0 to import it into the PlasticSCM 4.0 version. Regards, manu Link to comment Share on other sites More sharing options...
psantosl Posted November 8, 2011 Report Share Posted November 8, 2011 You need to use one of the latest 3.0 builds in order to use the fast-export... Stay tuned since we'll release updates Link to comment Share on other sites More sharing options...
hampsterx Posted November 10, 2011 Report Share Posted November 10, 2011 is there a secret switch to fast export or something? Seems it only exported changed files, not my original first commit and hence its missing all files not touched since we started using plastic v3. Eeek~ Link to comment Share on other sites More sharing options...
hampsterx Posted November 10, 2011 Report Share Posted November 10, 2011 ugh I tried adding all private items from my workspace (6k or so of files) to the /main branch but it wont merge them, gives an error message "An item with the same key has already been added". Figure probably should'nt have done this so serves me right I guess, hah Link to comment Share on other sites More sharing options...
manu Posted November 10, 2011 Report Share Posted November 10, 2011 Hi hampsterx, can you tell us how you are performing the fast-export operation? It should be straight forward, just cm fast-export yourRep@yourServer:Port and a fast-export.dat file will be created. Then use this file to perform the fast-import operation in Plastic4.0. Regards, manu Link to comment Share on other sites More sharing options...
hampsterx Posted November 10, 2011 Report Share Posted November 10, 2011 yup that was exactly the command I did, it's like it ignored changeset 0 (first import) or something. I think i'll hold off until next v4 release as I couldn't get v3/v4 installed side by side either (service error, and no I didnt go thru the config after install). Link to comment Share on other sites More sharing options...
hampsterx Posted November 17, 2011 Report Share Posted November 17, 2011 ok great to see the new release (4.0.237) installs side by side with plastic 3 Link to comment Share on other sites More sharing options...
cidico Posted November 17, 2011 Report Share Posted November 17, 2011 I just performed a fast-export and import operation and it seems that everything worked fine. I just had a little problem because i need to give a advancedquery permission in order to perform the fast-export command successfully. (Lost about 1 hour to identify this...) Another thing is, I build an VM using WS 2k8 R2 to test this command and I was using the Administrator user. The import went well and everything was beautiful, until I tried to update my DBrEx... It was giving me a error message saying that the user Administrator was "unactive". I just restarted the service and everything worked. Just for information. Link to comment Share on other sites More sharing options...
cidico Posted November 17, 2011 Report Share Posted November 17, 2011 Sorry about the error. It seems to be related to the license file used in the server. Just replaced the license that came with the installation by mine and worked like a charm. Link to comment Share on other sites More sharing options...
cidico Posted November 17, 2011 Report Share Posted November 17, 2011 I have to undo my older comment... The export command did not took all files A lot of files were not exported. FUUUUUUUUUUUUUUU Link to comment Share on other sites More sharing options...
hampsterx Posted November 18, 2011 Report Share Posted November 18, 2011 this may well be the source of my problems... 282 changesets retrieved 282 changesets will be exported 69 merges found 1 labels will be exported cs:0@/main 10/18/2011 5:46:24 PM is out of order 1 csets are out of order Changeset 1@/main 1/282. Elapsed 00:00:00.0160000 Changeset 0@/main 2/282. Elapsed 00:00:00.9830000 Changeset 4@/main 3/282. Elapsed 00:00:00.9830000 Changeset 6@/main/app mods 4/282. Elapsed 00:00:00.9830000 Changeset 7@/main/app mods 5/282. Elapsed 00:00:00.9830000 Changeset 8@/main/app mods 6/282. Elapsed 00:00:00.9830000 Changeset 9@/main/app mods 7/282. Elapsed 00:00:00.9830000 Changeset 10@/main 8/282. Elapsed 00:00:03.4320000 changeset 0 is out of order so perhaps its skipped, which would explain why i have everything except the initial import? -------- get this on import (v4) Error processing changeset mark 1. Parent cset mark: -1. Parent cset: -1 Object reference not set to an instance of an object. commit refs/heads/main mark :1 author tim <tim> 1318910173 +1300 committer tim <tim> 1318910173 +1300 data 29 Error: Object reference not set to an instance of an object. Link to comment Share on other sites More sharing options...
cidico Posted November 18, 2011 Report Share Posted November 18, 2011 I don't get the error message. Instead, plastic says everything ok but some files weren't exported. Very strange. Link to comment Share on other sites More sharing options...
psantosl Posted November 18, 2011 Report Share Posted November 18, 2011 Guys, Migration from 3.0 is not yet fully ready. I mean, it is doable but not straightforward. As you're doing, it is doable using fast-export and then fast-import. I'll focus the team on making it easier next week. It's been a loooong day today with the launch and everything Link to comment Share on other sites More sharing options...
cidico Posted November 18, 2011 Report Share Posted November 18, 2011 Thanks for the response Pablo! (You're really passionate to be here at 10:09 PM han?) It's just because I'm really excited about this new version. I'm trying to migrate my current project to the new version so badly that I forget sometimes that we need to wait a little. But, what do you mean for "doable" ? Is there another way to do it right now? Link to comment Share on other sites More sharing options...
Soho Posted November 18, 2011 Report Share Posted November 18, 2011 Hi, does this mean that we can expect a seamless upgrade option within a couple of weeks? That would be really great. It seems like a lot of my complaints about 3.0 have been addressed in 4.0, so I am really looking forward to try it out for real. Link to comment Share on other sites More sharing options...
wise1372 Posted December 13, 2011 Report Share Posted December 13, 2011 Hi, does this mean that we can expect a seamless upgrade option within a couple of weeks? That would be really great. It seems like a lot of my complaints about 3.0 have been addressed in 4.0, so I am really looking forward to try it out for real. I concur we have been waiting for 4.0 to resolve some issues we've been having and I don't see the logic in upgrading until support is built in. The fast-import/export is in my opinion a hack. Link to comment Share on other sites More sharing options...
psantosl Posted December 29, 2011 Report Share Posted December 29, 2011 Hi guys, Yes, the migration path from 3.0 to 4.0 is not as clean as I'd like it to be. You can call it a hack, and I'm the one to blame so, shame on me! No, really, I'm the one to blame, so feel free to share your thoughts and frustrations. That being said, I had some reasons which you can share or not but you know we try to do our best and we're totally committed to our users: you! We'll use the fast-export/import toolchain. I agree it is not as clean as it should, and we'll try to come up with an even better toolchain, maybe just a "migrator" doing it all for you. I'll try to explain the reasons and the underlying change in 4.0. Ok? Thanks all for your support and trust. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.