Jump to content

Search the Community

Showing results for tags 'replication'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Plastic SCM on Mac
    • Plastic SCM on Linux
    • Gluon
    • Git interop
    • Integrations
    • Community Edition
    • Branching and merging
    • Announcements
  • Plastic SCM 4.0 Beta (Closed)
  • Plastic Cloud
    • General
    • Configuration
  • SemanticMerge
    • General
    • License
    • SCM's configuration
    • Share your experience!
    • External Parsers
  • GitJungle
  • Method History for Subversion

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 18 results

  1. Hi, I'm using cloud edition, long time was solo developing now added second dev to team. Every time when second dev is trying to pull or push he is getting error "Unable to cast object of type 'System.Exception' to type 'Codice.CM.Common.ComException'". When in centralized mode he just don't get updates and his changes are invisible for me. Any suggestions how to fix this? EDIT: After few hours of searching, I found this post. Looks same, except he was getting error in the middle of download, my colleague getting error after getting meta data downloaded.
  2. Hi, I'm new to PlasticSCM Cloud Edition (coming from Perforce). Our goal is to setup a distributed version control system where the admin is "allowed" to create a local network server that replicates data to and from the cloud. Users should be able to sync with the local network repo instead of the cloud. They should also be able to sync their own local repo directly with the cloud. We want to avoid the situation where we setup a build machine, get the /main and have it all downloaded from the cloud. Our latest project was ~40 gb in size, so doing so each time and for each file sent by one of the 8 team members is a bit overkill, most of the time. For these cases, we would prefer to have a replication in our studio to connect to and benefit from the speed of our local network. Is this doable? I've been searching and trying for two days now without success (Clients are Windows, LAN server is Ubuntu 12.04). I always end up with errors such as: The client authentification mode (LDAPWorkingMode) doesn't match the server authentification (UPWorkingMode). The same error as above, but inversed when trying to connect to the cloud with a client setup as UPWorkingMode (all regardless of the Profiles I have setup). Explicit transaction expected, but found no transaction. FATAL Daemon - Access to path /home/parabole/FB_1236665269.dll" is denied. Also, it seems like Proxy require an Enterprise account. Is there another way to reduce the amount of data we have to load from the cloud? Cheers!
  3. Hello, We have two servers at remote locations. We want both the servers to be in sync. Right now we manually replicating the repos through "sync replication". Although this works, its extremely laborious as we have more than 25 projects. I read in this blog how telltale uses real time replication. Can you please throw some light on how to setup this up? thanks
  4. Hi I am moving my Plastic Server from a server to another. I used the SyncView to replicate all repositories/branches and everything went well. Here is my problem : I change a workspace selector to use server 2 instead of server 1. I can switch branches, etc I stop server 1 to check if the xlink fallbacks to the new server (which "Use relative server" should do) Plastic says that it is unable to reach server 1 to get xlink status All my xlinks are marked as "Use relative server", but it seems that they are all pointing at rep@server1 What can I do to change the endpoint of my xlinks without removing and re-adding them ? EDIT : It seems that if I recreate a workspace targeting a repository on server 2, the xlinks are relative, so it works. But my new question is : How could xlinks target server 2 without having to recreate all my workspaces ? I mean, we are 10 developers and have huge repositories. Thanks for your help, Maxime
  5. Good Day! I have gotten into a situation where I am unable to replicate a branch to my central repository due to error: The source branch can't have multiple heads. It's particularly sticky because this branch has been merged into another branch whose work I do not want to use. Branch A (this is the one I cannot push to the central rep) was merged into Branch B. Branch B was merged into Branch C. Now I have work in Branch C which was done by other developers which I cannot afford to lose. I am not able to delete changesets from Branch A so as to rebase it from the central server and redo all my work, therein. I know this is as clear as mud, so let me know what other info would help. Thanks, Tom
  6. I'm trying to pull from Plastic cloud to a local server. I get this error every time: I also tried exporting a replication package, but it fails immediately on step 3, with no error message (it just goes to status: canceled). And I'm experiencing that behavior on two machines. I assume there is some basic configuration issue?
  7. Hey all, I'm trying to get a distributed setup going between individual developers so that I won't have to host a centralized server somewhere. However, I'm pretty new to setting up this kind of tech, and I'm not sure how to actually connect to a plastic repo on another computer. I can't seem to find anything with specific details on doing that with Plastic, and I'm looking for any help anyone can give.
  8. All, I started looking at replication in Plastic to basically synchronize our Plastic server with a "backup" Plastic server on our LAN in a geographically different location. So far it seems as though I can't have Plastic replicate an entire repository the way I want it to. I would like to tell Plastic to replicate from Server A to Server B and pick one or many repositories to "keep in sync". We would like to use this kind of feature as a nightly backup of our Plastic repositories. So, would it be better to just replicate the SQL Server database that is storing our data instead of having plastic manage this? The reason I like plastic to do it would be to set up some kind of trigger to manage this, but I'm really not too sure how I would use a trigger here to do this. Ideas?
  9. I have a distributed environment using Plastic 4.x without any issues, I just upgraded to 5.x and now I am having a problem to Push my changes to a remote repository. Pulling changes (which I did first) was not a problem. Operation: Push Error description: You don't have permissions for operation replicatewrite. I also checked my permissions in the branch explorer for this branch, both sides are set to allow all (default). Any ideas on what could have caused this? I am not sure if it is related, but a few weeks ago using v4.x, a user from the remote location added a new branch which is showing up on my side as an outgoing change. Is there a file I can access to clean this up? Thanks, Jorg Gaubmann
  10. Hi! Why Plastic does not sync the labels created after the previous sync? I was setting up plastic to my collegue and after her first Pull, I created a new label but she was not able to get only the label. I think that only when I create another changeset she's going to get the new label. Same happens when I delete a changeset and branches. The difference here is that when I delete an cs or a branch, when I try to sync, plastic shows the cs's and branches as I need to pull from her. Maybe the delete operations could be handled by the sync tools... Thanks!
  11. I have a branch that seems to always want to replicate a couple of change sets, but I'm not sure why, and I'm not sure if this is something to be concerned about. Here: http://screencast.com/t/4MBL7Mz2vod, you can see that I'm replicating CS 358, but it's also including 317 and 318. Then here: http://screencast.com/t/BU0ceamz4mJ, I'm replicating CS 360, but again it's including 317 and 318. This branch almost always includes 317 and 318 when I do a replication (359 actually did not) and we're talking about a max of 15 minutes between replicating 358 and 360. Should I be worried about this?
  12. Good day - I was just wondering whether or not Attributes changes should trigger an 'outgoing' item in the Sync Replication view. For example, we use an Attribute named 'Promotion State' which indicates whether a branch is Development, Testing, Release Candidate or Production. After a Release Candidate has been signed off as good for Production, a release manager changes the Promotion State attribute to 'Production'. When he goes to the Sync Replication view, the branch does not show up as 'outgoing'. Should it? It's not critical, because we know enough to push the branch. I was just wondering. Thanks! Tom
  13. Good Day! I am currently setting up our shop as fully-distributed and, as of yet, we do not have the firewall permissions setup to allow push/pull between machines. Therefore, I am using the replication packages. My question is: When importing a replication package to my /main branch, is the merge done automatically? I ask because I was surprised to see two revisions on my item after I finished. Here is what I did: Both servers are in sync Create child branch from /main on PC001. Branch is named RepTest001 On PC001, switched workspace to /main/RepTest001 Checked in a change Created a replication package from /main/RepTest001 Copied PKG to SRV001 In the branches view, I right-clicked /main and selected Import Replication Package I selected the PKG file and pointed to SRV001 and the appropriate repository Import seems to work, as /main/RepTest001 now exists in SRV001. I did a diff on the branch and saw my change. Therefore, I merged from /main/RepTest001 to /main My item shows two revisions: the first seems to be the import and is accredited to /main/RepTest001. The second is my merge. These two revisions are identical. So, basically, does an import of the PKG to /main both import the branch and merge it to /main? Thanks! Tom
  14. Hey guys, I need some help with understanding replication. But first let me explain my request: I would like to create a virtual machine to act as a replication server on the domain for PlasticSCM in the event that our current build box (currently acting as our central server for PlasticSCM) has some kind of critical failure which would require a rebuild to that server and basically bring my development team to a stand still for a few days (at least). We have backups that are happening daily at different times of day, but I thought of also using Plastic's capability of replication to provide my team basically zero downtime. This seems like a neat feature. I would like to create an after-checkin trigger to replicate the changes in SiteA's repository to SiteB's repository. But it looks like there are some limitations or I dont fully understand how triggers work. It appears that I first have to create an after-checkin trigger that points to a batch file to get executed. But I want my batch to be as dynamic as possible and determine what branch the checkin is happening on and then push that branch's changes. In the below example, the branch being replicated is always /main. How can i make this dynamic instead of static in my batch file? cm replicate br:/main@rep:default1@repserver:localhost:8084 rep:default2@repserver:192.168.0.108:8084 So, ideally, when a checkin happens, and if there is an after-checkin trigger, theoretically, Plastic *could* tell me on what branch that checkin happened. So maybe we can do something like this below, where the replicate command reads in my command and replaces #branch# with the name of the branch the checkin happened on: cm replicate br:/#branch#@rep:default1@repserver:localhost:8084 rep:default2@repserver:192.168.0.108:8084 So, is this possible? Thanks!
  15. Good Day! So far, Plastic 4 is exceeding our expectations. I have only hit a few bumps and bruises. The latest one is; when using the Sync Replication, I am able to view the pending branches to replicate from my local server to the master server, but when viewing the pending branches from the master to my local server, I get an error: "There has been an unexpected error: 'The requested name is valid, but no data of the requested type is found <server>:8087 For more information check the server log." Here is the log info from my local server: 2012-02-06 08:29:41,940 INFO Channel - The exception was caught during PlasticTcpClientConnection.ProcessMessages: System.Runtime.Remoting.RemotingException, Tcp transport error., ThId: 5 2012-02-06 08:29:44,940 INFO Channel - The exception was caught during PlasticTcpClientConnection.ProcessMessages: System.Runtime.Remoting.RemotingException, Tcp transport error., ThId: 13 2012-02-06 08:29:44,940 INFO Channel - The exception was caught during PlasticTcpClientConnection.ProcessMessages: System.Runtime.Remoting.RemotingException, Tcp transport error., ThId: 14 2012-02-06 08:30:06,859 00000000-0000-0000-0000-000000000000 <server> INFO Operations - Get repository info 2 2012-02-06 08:30:19,315 00000000-0000-0000-0000-000000000000 <server> INFO Operations - Get repository info 2 2012-02-06 08:30:30,768 00000000-0000-0000-0000-000000000000 <server> INFO Operations - Get repository info 2 2012-02-06 08:31:02,945 INFO Channel - The exception was caught during PlasticTcpClientConnection.ProcessMessages: System.Runtime.Remoting.RemotingException, Tcp transport error., ThId: 5 2012-02-06 08:34:07,297 00000000-0000-0000-0000-000000000000 IWKSARMWS000003 INFO Operations - Get repository info 2 Here is the info from the master server: Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Codice.CM.Interfaces.IReplicationHandler.GetBranchesHeads(Int64 repId, BranchesFilter filter) at sm.a(BranchesFilter A_0) at Codice.CM.Server.Replication.ReplicationSynchronizer.a(BranchesFilter A_0) at Codice.CM.Server.Replication.ReplicationSynchronizer.GetSynchronizationStatus(BranchesFilter filter) at Codice.CM.Server.ReplicationHandler.GetReplicationSyncStatus(RepositoryInfo repInfo, RepositoryInfo remoteRepInfo, Credentials remoteAuth, BranchesFilter filter) at Codice.CM.Server.SecuredReplicationHandler.GetReplicationSyncStatus(RepositoryInfo repInfo, RepositoryInfo remoteRepInfo, Credentials remoteAuth, BranchesFilter filter) at Codice.CM.Server.TransactionInterceptor.GetReplicationSyncStatus(RepositoryInfo repInfo, RepositoryInfo remoteRepInfo, Credentials remoteAuth, BranchesFilter filter) 2012-02-06 07:34:09,810 ERROR Codice.CM.Server.ExceptionTracerSink - Dumping in-transit exception:There has been an unexpected error "The requested name is valid, but no data of the requested type was found: IWKSARMWS000003:8087". For more information check the server log. at Codice.CM.Server.TransactionInterceptor.GetReplicationSyncStatus(RepositoryInfo repInfo, RepositoryInfo remoteRepInfo, Credentials remoteAuth, BranchesFilter filter) at Codice.CM.Server.TriggerInterceptor.GetReplicationSyncStatus(RepositoryInfo repInfo, RepositoryInfo remoteRepInfo, Credentials remoteAuth, BranchesFilter filter) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext) 2012-02-06 07:34:42,167 INFO Channel - The exception was caught during PlasticTcpClientConnection.ProcessMessages: System.Runtime.Remoting.RemotingException, Tcp transport error., ThId: 5 Please note, that I am able to replicate via the UI (both directions, push/pull remote) with no errors. It's just the Sync Replication view that errors out. Thanks, in advance, for your guidance. Regards, Tom
  16. Good Day! I have gone through section 10 of the 4.0 manuals, but I think I still need a little guidance on the Sync Replication views. We are fully distributed, each developer having his own server (very cool!). If a developer replicates a branch (TASK0001) to the master server, when I look at the Sync Replication view I see TASK0001 as 'incoming'. Then I merge TASK0001 to /main on the master server. I then pull /main from the master server to my local server. Now, at this point, I have all of the developer's TASK0001 changes in my local /main branch. HUZZAH! However, I still see TASK0001 as 'incoming' in my Sync Replication View. Our rules are that we only pull the /main branch from the master server. We will never pull TASK0001. So, how do I get TASK0001 out of my 'incoming' list, or am I just supposed to ignore it? Thanks in advance! Best regards, Tom
  17. I have an 'after-checkin' trigger that calls a script that regenerates and deploys a website from a specific branch. That works ok when you checkin to the repository directly, but if you replicate changes from a local repository, it does not seem to call the trigger. Is this intended behavior? If so, is there any way around this limitation? There does not seem to be any triggers that would catch such a scenario. Thanks! Edit: I would guess we need a trigger similar to git's post-receive hook, or hg's incoming hook.
  18. I'm having trouble pulling changes to a remote PC, I get the following error: I've tried doing an update operation, but that doesn't help. I've pulled changes in the past, but I'm pretty new to Plastic so I'm not sure if this is a bug or I'm just missing something.
×
×
  • Create New...