Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>According to your comments, what you need is to take advantage of Xlinks.</p> <p>Xlinks in Plastic SCM are basically special directory entries to a path on a given changeset, so that the "cset immutability" is preserved.</p> <p>There are two kind of xlinks:</p> <ul> <li>Readonly xlinks: which means you just use the linked code to build but you won't modify it while working on the source tree linking it.</li> <li>Writable xlinks: which means you'll be modifying the linked code while working on the project. They're similar to git submodules but "done right", which means, plastic deals with all the plumbing to update the parent to the new cset created on the child.</li> </ul> <p>Answering your question: yes, right now you'll need 3 repositories to set up the project you're working on: 1) Program Repo 2) Module Dev Repo 3) Module Incl Repo (which is the one the other two will be referencing)</p> <p>The workflow with readonly xlinks is:</p> <ul> <li>You create the xlink to you "module incl repo" on "program repo", something like:</li> </ul> <p>cm xlink src\incl / 23@ModuleIncl@yourserver:8087</p> <p>Which means you're creating an xlink at src\incl pointing to the changeset 23 in repo "ModuleIncl".</p> <ul> <li><p>You checkin to commit your newly created xlink</p></li> <li><p>Update your wk to get the code from the xlink (it is not done upon ci)</p></li> <li><p>Then, if at some point you need to update to, let's say, cset 30, you'll edit the xlink (from CLI or GUI) to point to the new one:</p></li> </ul> <p>cm xlink -e src\incl / 30@ModuleIncl@yourserver:8087</p> <p>And this will be enough for the readonly workflow.</p> <p>You can find more info about Xlinks here <a href="http://www.plasticscm.com/releases/4.1/manuals/en/xlinksguide.pdf" rel="nofollow">http://www.plasticscm.com/releases/4.1/manuals/en/xlinksguide.pdf</a></p>
    singulars
    1. This table or related slice is empty.
    1. POCode Sharing in Plastic SCM
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USpablo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCode Sharing in Plastic SCM
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks. Unfortunate that you can only link full repositories.
      singulars
      1. PO
      1. USKempeth
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload