Jump to content

Fleer

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Fleer

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Carlos, Just to clarify, I wasn't creating a new changeset in the Xlinked repo, I was editing it directly from the parent (projects) repo. And the changes were not being picked up in the parent (projects) workspace on different machine when using the partial update code above. Cheers Paul
  2. Hi Carlos, Thanks for the quick reply. I might have to restructure how I do things, but currently I am using something like this. projects project1 (Xlink A) Unity (Xlink B ) project2 (Xlink C) Unity (Xlink D) I push new code to Xlink B or D from an overall, local, projects workspace through the GUI (let's say moving it from Changeset 1 to 2) I then run the following code in a projects workspace on a build server cm partial configure +/project1/Unity --ignorefailed cm partial update /project1/* And the Unity Xlink has remained at Changeset 1 I understand it may be easier for me to restructure so that I have individual workspaces for each Unity repo, and then run full updates on those (maybe?), however I'd still appreciate some guidance as to why the above fails to work or some other suggestions. Cheers!
  3. Hi there, I want to only 'cm partial update' on part of a larger workspace (to isolate projects, and save on server space), but I've noticed that my Xlinks are not updating to their latest changeset unless I run a complete 'cm update' on the whole workspace. I'm sure there is some reason for the difference in behaviour, but am I able to achieve the same thing with cm partial and some flags (that I cannot find/work out) or am I attempting the impossible? Cheers!
×
×
  • Create New...