Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Although TeamCity has a good view tracking of dependencies on a per-build basis, I'm not aware of a page in the UI that allows you to see a list of build configurations that depend on a given "parent" configuration. You can of course view each individual configuration to find this out, but that may not be feasible in your large deployment.</p> <p>If you'd like to access this information in a single place or programmatically, it's stored by TeamCity in a <strong>project-config.xml</strong> file in your &lt;TEAMCITY-DATA-DIR&gt;\config\&lt;PROJECT-NAME&gt; directory.</p> <pre><code>&lt;project id="project1"&gt; &lt;build-type id="bt1" name="Parent"&gt; ... &lt;/build-type&gt; &lt;build-type id="bt2" name="Child 1"&gt; ... &lt;settings&gt; &lt;dependencies&gt; &lt;depend-on sourceBuildTypeId="bt1"&gt; ... &lt;/depend-on&gt; &lt;/dependencies&gt; &lt;/settings&gt; &lt;/build-type&gt; &lt;build-type id="bt3" name="Child 2"&gt; ... &lt;settings&gt; &lt;dependencies&gt; &lt;depend-on sourceBuildTypeId="bt1"&gt; ... &lt;/depend-on&gt; &lt;/dependencies&gt; &lt;/settings&gt; &lt;/build-type&gt; &lt;/project&gt; </code></pre> <p>In the above example, you could look for any <strong>build-type</strong> that had a <strong>settings/dependencies/depends-on</strong> node with a <em>sourceBuildTypeId</em> matching your parent configuration <strong>id</strong>. This approach should still work even if your dependencies span multiple projects, as the build type ids are unique on the TeamCity installation.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

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