Jump to content

Search the Community

Showing results for tags 'xlink'.

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

  1. Hi, I am looking at breaking up an existing project in to a couple of repositories so that we can make use of xlinks to share code between the original project repo and a repo for a new project. Whilst looking in to this I came across some issues that I have not been able to resolve and was hoping someone could provide some help. Our team has a mix of people creating their repos in a centralised way with @cactus@cloud and others that set up a local repository and use a sync view to push/pull to the repo in the cloud. For the new setup I have broken up functionality in to a couple of new repositories, "Tech" and "Tools" which contains common cross-project functionality. In the original project repository (in my local repository) I created an xlink to the new Tech repository as follows: cm xlink -w Source/Tech / cs:1@Tech@cactus@cloud I have committed and pushed those changes to the cloud repo. I have a second workspace for this project that is setup to track the cloud repo directly. In that workspace I am able to update the workspace as normal and i can see that the Source/Tech folder is populated with the contents as in changeset 1 of the new repo as expected. However in my other workspace which is set up as a local repo tracking the cloud repo that Source/Tech folder is empty. According to your documentation here you should update the workspace by clocking "update woekspace" in the GUI but as far as I'm aware this button is not available when creating local repos and updating via a sync view. I came across another forum post here which seems to be discussing something similar but in their case their xlink appears to be to a local repo whereas I want to set up my xlink to the cloud repo. Do I still need to adjust my sync view or create a new sync view to get this working? What is the process for syncing with an xlink at a cloud repo on a workspace for a local repository or is this not supported? Thanks Tom
  2. Title kind of says it all. We're trying to insert a submodule into our Plastic Cloud repository, but all the documentation seems to indicate that we need to be running our own Plastic SCM server. So far, our solution is to create the folder for the submodule, ignore it, and keep it updated with our other git clients (we use plastic for one very large project we had no hand in creating, and bitbucket for everything else)
  3. Hi, I've been having issues syncing a plastic repository with git since I added an XLink to the project. There is a similar post here where a user is encountering a similar issue although I wasn't able to resolve my issue through that post. The issue is this. I have 2 plastic repositories, 1 called "LevelEditor" and another called "Core". These two repositories are both synced with two git repositories hosted on bitbucket. This syncing has worked just fine, but recently I created an XLink in the LevelEditor project, which points to the Core repository. Since that point I have been unable to sync LevelEditor with its git equivalent, receiving the error: "The equivalent Git repository for 'CLIFTEK_CORE_REP@localhost:8087' has not been defined. The xlink cannot be pushed. Please, add the equivalence inside the submodules section in the configuration file 'C:\Users\Thomas\AppData\Local\plastic4\gitsync.conf'." My understanding having read the thread I mentioned earlier and the documentation here is that I need to have the submodule information defined in this gitsync file. I did not actually have a gitsync file but I created one at the given path. I then proceeded to add the submodules information. This is what the file looks like: [submodules] https://bitbucket.org/cliftek/core/ -> CLIFTEK_CORE_REP@localhost:8087 writeable:true relativeserver:true Unfortunately this has had no effect for me and I still receive the exact same error as before whenever I try to sync (I have restarted the plasticscm server and client a few times). I am sure that I have got the syntax wrong or something similar but can't get it to work. Could you provide me with some assistance to help rectify this issue please? Thanks, Tom
  4. We have recently set up a project where a directory within that project is an xlink to another project. The files within this xlink are meant to never be edited, so we have the xlink on read-only. Whilst this is fine to prevent any changes to the files on source control, we need to enforce that our users cannot modify the files locally at all. Ideally this would be with a windows file lock applied recursively to the directory. Is there a convention for doing this within plastic? The closest idea I have is to use client-side triggers to file lock the directory, but I cant see a way of applying the trigger to a single repository? It feels like I am probably missing an element of Plastic SCM to solve this problem? Any help much appreciated! Thanks
  5. I have a question about merge and conflict with XLink. I would like to explain why after merge conflict exists. The problem/description: I have two repositories “TestPB” and “TestPB1”. The “TestPB” repository has XLink for the “TestPB1”. I have two branches to which the same change is added. Next updates the XLinki in the “TestPB” repository and merges like this: In this case, after the merge there is a conflict for XLink. I would expect that there will be no conflict because start and end changeset are the same, additionally the change (cs:23) was add in two branches - “TestPB1" repository. I am asking for help in explaining the merger or how to solve the problem for automatically merge
  6. I am having some trouble finding clear documentation on the following: - Is it possible to update a workspace, but NOT a writable xlink? - Is it possible to update an xlink directory, but nothing else in a workspace? Thanks in advance!
  7. 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
  8. Hi, I am using Plastic with Unity in macOS. At this moment we are using a few repo for project (main and additional packages). To the main project I connected by Xlink (in command line) another repo. However, I found two bugs: 1) I added a new label (1.0.1) to commit and push it to the cloud but Xlink doesn't see it. The previous label (1.0.0) is visible by Xlink - it was created by another person on Windows 2) The label 1.0.1 is connected with commit with "Object name 6". I connected it by changes number but some of the changes was not visible. However, when I connected to "Object name 7" (cm xlink -e NodeEditor / 7@RGNodeEditor@servername@cloud) which doesn't exist in the repository everything start working...
  9. So we're having a small workflow issue when working with Unity and a series of xlinked projects. I'll explain the problem then what I think is the cause. When making a check in, quite often a branch will be made in one of the xlinks (as expected) but it won't actually have a change set checked in at the same time as the one in the master project. When performing a sync to other machines, this causes issues as the branch doesn't get replicated unless there is a changeset in it, and checking in and switching changesets will fail due to this empty branch being missing. So what I think is causing the issue, is there are a lot of files that get 'touched' by Unity, so Plastic adds them to the check in process, even though the file contents are identical (which you can check by opening a diff window for them). When Plastic goes through it's Check In process, it sees that an item in an xlink is modified, creates the branch on the xlink, then optimises the actual checkin because the files are identical, leaving the empty branch on the machine, but as a dependency for the master project. We can currently work around this by going back to the machine that has the empty branch, making an explicit change to a file and checking that in so that there is a change set, however this isn't an ideal workflow and we've come across this several times now. If you have any ideas on ways to prevent this, or if this seems like a bug and you need reproduction steps, please let me know. Thanks!
  10. It is said that one of the best practice to use VCS is to keep all submissions compilable, or more strictly, passes unit tests. However, consider this situation: I changed the version of xlinked subproject. The new code in subproject may have major changes, and may be incompatible with the codes in parent project. Theoretically I should modify code in parent project to fit with the subproject before submit. However, before I submit the xlink verison change, I cannot get the new code in subproject. How can I solve this dilemma? Thanks!
×
×
  • Create New...