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
    • 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


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 6 results

  1. 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
  2. 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.
  3. 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
  4. Hey guys, I'm looking for a way for changesets to automatically sync to the cloud in plasticSCM cloud edition. As in, I don't want to have to go to the sync to cloud button, tap the sync view, and push/pull everytime. Is there a way to set up a timer or something so it periodically checks the cloud server for changes and pushes up if there are no conflicts? thanks.
  5. We're currently evaluating the Team Edition for a small team. Everything was going well until my colleague and I had both made changes to different files. These files were checked out and do not conflict with each other. One colleague submitted their changes while another was working on their checked out file. When the later colleague was ready to push out their changes, they were unable to due to the fact that Plastic Cloud does not offer merging abilities and that he was out of sync with the cloud repo. When he tried to download the latest from the cloud repo, he was unable to as well. In both cases, he received the error message: This lead me to this article with somebody having the same issue: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide.shtml#Serverconfiguration The solution was posted by a community member which was: This wasn't the best approach as it effectively negates the feature of checkout'ing a file and locking the file when someone is working on it. Everything about Plastic is fantastic and I'm liking it far more than Perforce except for this seemingly crucial necessity of co-working on files simultaneously on Plastic Cloud. Why is it so difficult to do this with Plastic Cloud? If anyone has figured out a work around, please let me know. The docs aren't helping as their solution seems convoluted. Thanks
  6. Hi, I have a distributed setup with Cloud Edition where I use a sync view to update my local repo to and from the cloud. I'm looking into using the code review feature as part of our development process. With a code review associated to a branch, if there are no new changes for the branch, the sync view won't show any pending changes when comments have been added by a developer and pushed to the cloud server. I know that I can manually push and pull the branch to replicate the code review changes but, shouldn't sync views show that there are pending changes in a code review associated with a branch and push/pull them appropriately? My only alternative at the moment, since I don't know which of the code reviews have new comments, is to manually pull all of the associated branches, open the reviews, and see if there are any new comments which is making reviews very impractical. Thanks!
  • Create New...