REST: Getting the inbound dependencies

Hi,

the REST API makes it easy to get outbound dependencies, e.g. get the build(s) that a given build depends on. I need currently the inbound dependencies, e.g. other build(s) that depend on a given build.
Is that possible?

Olivier

5 comments
Comment actions Permalink

Hi Olivier,

There is no such REST API request in TeamCity. Could you please describe your use case? Why do you need the list of builds that depend on a given build?

0
Comment actions Permalink

Hi Alina,

In my particular case, I use a build to generate paremeters, which are propagated to depending builds using dep.*, and I need to find out programaticaly which builds have used these parameters for a specific run.

A more general example is when when you need to track where the artifacts produced by a specific build have been used.

0
Comment actions Permalink

Hi, due to performance concerns TC doesn't offer any way to find what build configurations depend on this particular one.

The only way you can find dependent configurations is to use particular build's dependencies tab (or build chains tab of build configuration, which is a summary), but this is not currently possible via REST API.

0
Comment actions Permalink

Hi Sergey,

OK, too bad, but thanks for the feedback.

I still don't understand why it's not possible to offer the same information over REST than in the web interface. Only the presentation is different, it's the same data, so performance shouldn't be a problem. Or I am missing something?

And if it's not available from the server, I have to use brute force (e.g. fetch all the dependencies of all builds) from the client to find out this information, which is certainly much worse from a performance perspective than doing this on the server.

Message was edited by: Olivier Croquette

0
Comment actions Permalink

This is not possible, partially because REST API is designed to respond quickly, which is not possible, when calculating build chains.

0

Please sign in to leave a comment.