Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It looks like you have two different issues you need to address: </p> <ol> <li>How to set up your VCS for your build configuration </li> <li>How to handle your external libraries</li> </ol> <p><strong>For your VCS</strong>, leave your setup as you have it - at the root of your repository. In each build configuration, you can add <a href="http://confluence.jetbrains.net/display/TCD4/VCS+Checkout+Rules" rel="nofollow noreferrer">checkout rules</a> to prune your checkout to the right folders. </p> <p>For instance, you can use the following to make the trunk folder the root folder of the checkout: </p> <pre><code>+:trunk=&gt;. </code></pre> <p>Or for a branch, you can do something like: </p> <pre><code>+:branches/featureset=&gt;. </code></pre> <p>You can add multiple checkout rules if desired, including adding any files/folders from your extlib folder:</p> <pre><code>+:extlibs/dependency-2.5.3=&gt;.libs/dependency1 </code></pre> <p>You can even remove files/folders using checkout rules:</p> <pre><code>-:trunk/files-not-needed </code></pre> <p><strong>For your external libs</strong>, as stated in other answers, you can include external folders using SVN. However, I would not get heavy handed with the inclusion of the entire extlibs folder. Only include the specific library revisions that you need to build the project. Also, make sure your extlibs folders are well-protected from change. By being fine-grained about your externals, you can avoid the issue of trying to build an old version because your project will be linked to the correct version. If you have triggered builds enabled, you will also avoid a library change triggering a build. For example, you could configure your snv:external libs like so:</p> <pre><code>libs/dependency1 svn://yoursvnserver/svn/extlibs/dependency-2.5.3 libs/dependency2 svn://yoursvnserver/svn/extlibs/dependency-rc-2.4 </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POTypical SVN repo structure seems to be sub-optimal for continuous integration
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UScodeprogression
    1. UScodeprogression
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTypical SVN repo structure seems to be sub-optimal for continuous integration
      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. VTAcceptedByOriginator
    1. COI do like the idea of keeping extlibs where it is. At my previous job, we didn't keep them well-protected from change, but it was just known that things there shouldn't be modified often, and when they are, the entire team needs to be notified. Thanks for the info. I haven't been able to focus on this issue recently, but I will review your suggestions soon!
      singulars
      1. PO
      1. USDave
    2. COI didn't mean to give the impression that you needed to move the libs, but instead use the svn:external commands to import the specific dependencies you needed. I do hope the information is useful.
      singulars
      1. PO
      1. UScodeprogression
    3. COAlso, you can use the checkout rules to only pull the extlibs folders you need. (It sounds like you are linking to that folder structure in development.) You could add each as needed, but may be a maintenance problem when you start needing additional libraries.
      singulars
      1. PO
      1. UScodeprogression
 

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