Jump to content

Search the Community

Showing results for tags 'sync'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Unreal Engine
    • 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
  • PlasticX Early Adopter Program's General Feedback
  • PlasticX Early Adopter Program's Issue Reporting
  • PlasticX Early Adopter Program's Feature Requests
  • PlasticX Early Adopter Program's Announcements

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 5 results

  1. Hello there! I'm new to Plastic and try my best to solve this problem to myself, but atlast - i'm stack. So, what's the proble: I'm trying Plastic in distributed mode to work with an existing project When the program was launched for the first time, the wizard for creating the first workplace opened - I selected the mode, indicated the name and address of the local repository, and selected the one in the cloud The workplace, repository and sync rule was created, but when i try to look at the branches of cloud to pull whem by the sync i get this error: Also when i try to look at my local profile setting i got this error: Cannot retrieve the profile from local. Details: *one from below* So,I looked at the log and there was an error (the second replaced the first after several reinstallations of the Plastic) : ERROR PlasticRestApi - There was an error while calling 'https://local:7179/api/v1/login/accesstoken': This host is unknown. (local:7179) or ERROR PlasticRestApi - There was an error while calling 'https://local:7179/api/v1/login/accesstoken': The remote name could not be resolved: 'local' And the server log (plastic.errors.log.**) have: (null) (null) ERROR Organizations - Organizations configuration file 'C:\Program Files\PlasticSCM5\server\organizations.conf' does not exist! What I did trying to fix them: I test this port (local:7179) in cmd (netstat) and powershell (Test-NetConnection) - it did not find it I checked the services from Plastic - they work, even restarting Added this port and services to the exceptions in the firewall and my antivirus Created an empty 'organizations.conf' file - because of this, the rest of the functionality of the program stopped working and the server simply gave an error about this file Clear (with delete the the 'PlasticSCM5' folder) reinstalled the program But nothing could fix the problem, only the error text changed. What could be the reason - why the local server cannot start normally? Or is the problem something else? For now, I will work in centralized mode, like the rest of the team, but I still want to make distributed work as well. I have attached the server and client logs. plastic.relevant.log.20220623.txt plastic.debug.log.20220623.txt plastic.debug.log.20220623.txt plastic.errors.log.20220623.txt
  2. So I have a Unity project that I have been working on for some months now. Prior to my switch to Plastic, my teammate and I were using Unity Collab to work on the project together. After switching to Plastic, I made a few changes and checked them into the local repo. Before syncing to cloud, Plastic told me that I should pull incoming changes, which were the 37 changesets we had made using Collab. Pulling caused no changes to my project, as I already had those changes on my computer. After pulling, I have been attempting to sync the most recent changes to the cloud, however I get the following error: "The source branch has two heads. Merge from cs:51fea8e5-3a76-4bbf-b648-070ad2e89a13 to br:/main to unify the heads". I understand why it is giving me this issue, however I am not sure what to do. Under branch explorer, there is only a single branch. When i look at changesets, It goes 1, 2, then jumps to 40, which is the most recent change. I have no clue to where to locate cs:51fea8e5-3a76-4bbf-b648-070ad2e89a13 in order to perform the merge. I have tried merging all of the visible changes sets and all of the bubbles shown in the branch explorer, however it always tells me the the files are already there and there is nothing to merge. I have some similar posts to my situation, however I have not been able to solve my issue by looking through them. I am still very new to working with Plastic, and I would really appreciate some help to get my project back on track.
  3. Hello, in our setup we manually push selected branches from our premise server to the cloud. But we want to pull all branches from the cloud to our server. The processes run automatically via a timed batch script. My pull command looks like: cm pull "/main/dev@repo@org@cloud" repo@server:8087 I tried to use wildcards (*, %) like cm pull "/main/dev/*@repo@org@cloud" repo@server:8087 -------------------^ but nothing worked. Is there some way to pull the (child) branches recursively? I put "child" in parentheses, because we are fine with pulling all branches from the cloud (we just don't want to push everything there). The more complicated way I can think about would be: getting a list of all cloud branches and then pulling each branch separately. That would be weird and uncomfortable and I think there must be another way (GUI "sync" can do this, is there a log of commands called from the gui?). Thank you all
  4. This is my first day of using Plastic SCM, so probably I'm doing something wrong, but it would be nice if such basic features didn't require hours of research. I made a branch for my changes, switched to it, done some work, went to Pending Changes tab, chosen the files I want to commit, added a nice description of what I did and clicked Checkin. So far so good. After that I opened Sync to Cloud tab and clicked 'Push Visible' and got an error: So i clicked 'Pull visible', hoping that it will pull the files from cloud and let me solve potential conflicts locally. I got a nice popup that told me it's 100% complete and everything was OK. I clicked "Summary" and apparently nothing has been pulled, as Count for all positions in the list was equal 0. I closed the popup and went back to Sync to Cloud tab. Same Incoming changes as before pull were still visible on the list, no matter how many times I clicked Refresh, retried pushing and pulling, updated the workspace and relaunched the client. Am I doing something wrong or is it a malfunction? Btw. also uploading images to the forums doesn't work. Each time I try I get "There was a problem uploading the file." message.
  5. Hi, I have noticed that when you sync repositories, the changeset numbers no not necessarily match up on the different servers. At first this was just an annoyance due to using Plastic for 3 years (without replication) prior to this point and getting very used to using CS numbers to discuss work in the depot and also as the main descriptor in automation tools. However I now have a use case which is a little more than annoying. First of all, to discuss the setup in case that has any bearing on it. Our central repository is in the Plastic Cloud. Our distributed team do a mix of connecting directly or setting up a sync view locally. Personally I have two separate servers syncing against the cloud server, one on my development machine, the other on my CI system. I have chosen to use the standard rather than the cloud edition for both of these. My two replicated repositories have differing CS numbers than on the cloud and also different from each other. It's never been more than about +/- 3 numbers, but different. My CI system is Jenkins based and the pipeline uses smartbranch to identify and sync on the correct branch/CS number using "smartbranch "%BRANCH%" changeset "%CS%"". I don't think there is another way to do this? Therefore in my CI system I need to ultimately work with CS numbers. For CI tasks this is not an issue as the system uses it's own replicated view of the Plastic server in isolation so can just use the numbers that it sees and everything is fine. The issue comes when people want to interact with the CI system. One issue is that it can be confusing to the user when a job is described by it's CS number and that does not match up with what they see in Plastic. For this issue, I am thinking that I will have to drop using the CS number completely in reports that are generated by the CI system and instead just use the comment from that CS? This will make it a lot harder for users to identify what CS a job was built against. Is there not some other globally consistent identifier for a CS? I have considered labels but I think that could end up very messy as we would end up with a lot of them. However my real problem is when users want to request that the build system perform a special build for them. How do they identify the CS that they want building? They will have no way of knowing what CS number is being used on the (invisible from them) local Plastic server in the CI system. I'm thinking that I will have to take the name of the server that they are referencing the CS number against and then somehow look-up what the equivalent CS number is on the replicated server in the CI system? Is this even possible? If someone is able to shed some light on this, it would be much appreciated. Thanks, Kieran
  • Create New...