Jump to content

rclark

Members
  • Content Count

    1
  • Joined

  • Last visited

Community Reputation

0 Neutral

About rclark

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I have issues with xlinks where referenced changesets were deleted, causing xlinks to be 'corrupted' and point to Guids instead of changeset numbers. Likewise, the wxlink'd repository gives a Guid prefix to the repository name. Example being: We have nested xlinks, which have resulted in only one of the nestings having corrupted xlinks. For example, our common xlink structure between repos is: RepoA & Repo B rely on Repo3, Repo3 relies on Repo2, Repo2 relies on Repo1. RepoA will show a corrupted xlink for Repo1, but Repo2 won't. Normally we would only resolve the top level xlink (RepoA would update the xlink for Repo3), but due to the corruption we have to resolve it out of order. This has caused a slew of issues: loss of branch expansion default rules, automatic xlink commits which cause circular dependencies, etc. What I believe to be the main issue is when commits delete the default branch expansion rule. For instance, what should be this: ...will receive a commit during automatic xlink commits which change the rule to this instead: When losing the default branch rule, our external builder (TeamCity) fails to resolve branch xlinks, causing all builds to fail. With all of this said, I'm looking to delete our xlinks and recreate them—but I have no way to delete an existing xlink using the Plastic GUI (v9.0.16.4608). When attempting to create an xlink over the pre-existing one, it tries to reference the repo itself as source and destination, instead of the provided source repo—which gives the error "A repository cannot be loaded inside itself." How can I delete these 'corrupted' xlinks and create new ones? ---- Our Senior System Admin, @rodgeralley, can add more info on the Plastic setup.
×
×
  • Create New...