Search the Community
Showing results for tags 'plasticscm'.
Found 2 results
Hi everybody, I'm afraid I did a big mistake on one of my repo. I have a repo called "My_repo_A" which has a XLinked sub repo called "My_repo_A_shares". This sub repo "My_repo_A_shares" is synced with a repo on github. But tonight, after a hard work week, I synced by mistake the parent repo "My_repo_A" with the same repo on github. That resulted in a warning like "the branches have to be merged before being able to push with gitsync again ...". Hopefully there are no problems on github, but in plastic a lot of commits are duplicated with different guid, and branches have two heads ... So ... the winner is me ! I know ... but is there a way to cancel a gitsync ? Thanks a lot for your help.
Hello everybody, I suddently have a problem with one of my Plastic SCM client on Windows. Everything worked well, but since last week I can't connect to my Plastic server anymore. Nothing changes in server config nor in my client config, but now I've got this message "The remote certificate is not valid according to the validation procedure" (see attached picture). The server has an attached domain with a valid, not expirated, certificate. But, as my client is on the same network as the server and as my box can't do loopback (domain name pointing to itself) I have an entry in my client host file to redirect domain name to local server IP address. This worked for more than 3 years without problem. The only thing that happened last week is that I used my PC out of office, so I removed the redirect line in my client host file in order to do my commit through "real" internet. This also worked properly. But a few hours later when I restarted Plastic from my office again (with local host redirection), it began to display the error message. Server and clients were in version 188.8.131.5204, I updated my Windows client to 184.108.40.20668 but the problem did not disappear. Two other clients (on Mac) don't suffer from the problem and continu to reach the server without problem, locally or through internet. So my question is : is there a kind of certificate cache on Windows client ? ... Perhaps wrong data was cached when I came back to my office. I tried to clear windows ssl state in "internet options" but it had no effect. Any idea ?