roadrunner Posted December 8, 2011 Report Share Posted December 8, 2011 Is there a feature available to automatically force a sync to a destination repo? The synch repos would be a useful tool to keep an offsite backup of the repository on an automated basis (push-only to the destination) Link to comment Share on other sites More sharing options...
psantosl Posted December 8, 2011 Report Share Posted December 8, 2011 A trigger? A checkin trigger spawning a new proc (don't make it wait) and launching a push Link to comment Share on other sites More sharing options...
roadrunner Posted December 9, 2011 Author Report Share Posted December 9, 2011 Do you have an example that would force the sync to happen on a checkin? Link to comment Share on other sites More sharing options...
psantosl Posted December 9, 2011 Report Share Posted December 9, 2011 The trigger will give you the branch name It would be as simple as a .bat with: start cm replicate BRANCHNAME your_repo@yourserver:port --push Link to comment Share on other sites More sharing options...
roadrunner Posted December 18, 2011 Author Report Share Posted December 18, 2011 Hmmm... not quite drop dead simple. Sync from the Plastic GUI works great, but when running from the server, it needs to be able to execute from the context of the user that the service is launched under.. since it's running under Local System, for Windows 7 this means creating a client.conf in C:\Windows\System32\config\systemprofile\AppData\Local\plastic4 But then for remote authentication... I changed from Local Users to User/password based security and created a user with the same name/password on both sides, and then copied client.conf (with user/pw configured in <SecurityConfig> section) to the system profile and restarted the servers. When syncing manually from the client, it works fine, but when syncing from a trigger (after-checkin type) then I get unknown user error. Link to comment Share on other sites More sharing options...
manu Posted December 19, 2011 Report Share Posted December 19, 2011 Hi roadrunner, If the server machine is only to be used to perform replication tasks I prefer to copy the client.conf inside the PlasticSCM client installation path. By default plastic is going to search first if there is a "client.conf" file in the client installation path. So you only need one "client.conf" file and it will be used by all the system accounts. Regards, Manu. Link to comment Share on other sites More sharing options...
CodingGorilla Posted December 19, 2011 Report Share Posted December 19, 2011 I was looking for something like this as well, as command line option equivalent to the GUI's "Synchronize all.." would be really handy. Right now if you have 15 branches, your scripts would need to 'know about' all your branches so that it can synchronize them. I was looking for a command line equivalent because the "powers that be" are concerned that people won't push their changes regularly and therefore risk losing some changes when a developer's machine explodes (which is no different than checking in changes in SVN, I pointed out ). So my solution [was going to be] that we put a scheduled task that on everyone's machine that does the "Synchronize all...". Another item for the To-Do list... Link to comment Share on other sites More sharing options...
manu Posted December 22, 2011 Report Share Posted December 22, 2011 Hi CodingGorilla, it was already in the To-Do list We want to give the CLI the same functionality as the "Sync view", in this way the central server ca, for example every night, run the Sync command to retrieve all the changes from all the distributed developers. Link to comment Share on other sites More sharing options...
CodingGorilla Posted December 22, 2011 Report Share Posted December 22, 2011 While you're at it, can I suggest a "Sync all sync views command" as well. Right now, in the GUI, you have to go down the list of views; click view a, click Sync All, click view b, click Sync All. If you could either multi-select the views or have another button that synchronizes everything that can be synchronized that would save even more time. This would apply [hopefully] to the cm command as well. This would save a lot of time, especially in scripting. Otherwise every time there's a new repo or a new developer, you have to set up the sync + a new script to handle it. Link to comment Share on other sites More sharing options...
manu Posted December 22, 2011 Report Share Posted December 22, 2011 Good idea CodingGorilla! Link to comment Share on other sites More sharing options...
psantosl Posted December 25, 2011 Report Share Posted December 25, 2011 Enter it in uservoice Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.