how to get list of build configurations that have no compatible agents

How to I get a list or report of all build configurations that have no compatible agents?

7 comments
Comment actions Permalink

Hi,

Could you please detail why do you need the compatibility information?

You can find such information on Agetns->Matrix tab, which shows compatibility data for all configurations and agents on a single page.

It is impossible to get such list using UI or REST API. We have the feature request, please watch/vote for it.
Current workarounds would be:

  • write own Java plugin to expose the data in the most suitable format or build the report tight in TeamCity;
  • parse web UI pages content (not recommended).
0
Comment actions Permalink

I'm not sure the agent matrix tab provides the information I want, because it's based on build history.

We have build configurations that, because of un-maintained agent requirements (agent name, OS, environment variables, etc.),  no longer have any compatible agents to run on.   Occaisionally, these get triggered, and they sit in the build queue because there are no compatible agents.   When we find them this way, we fix them.   

However, there doesn't seem to be a good way to do this proactively.  

As a contrived example:  we've just renamed a build agent - which build configurations does this prevent from running now because they had a build agent requirement with this name?

0
Comment actions Permalink

Shane,

I second your request. In the past we've requested the same thing here: http://youtrack.jetbrains.com/issue/TW-24009 and it is now tracked as http://youtrack.jetbrains.com/issue/TW-26790 (which Alina mentions above).

I'm specifically mentioning TW-24009 (although it's closed) because unlike TW-26790 it has a detailed description of the feature that's conspicuously similar to yours.

Hope that helps.

Best,
Sam

0
Comment actions Permalink

Hi Alina,

This doesn't really help to get the list mentioned in the topic. Imagine the following situation:

  1. You have several agents with slight differences in configuration, including agent parameters and env. variables.
  2. You need to remove one or several agents (hardware decomission/reallocation).
  3. Now you need to get a list of configurations that you'll no longer be able to build.


Thanks,
Ondrej

0
Comment actions Permalink

Hi,

Yes, I understand the difference. I’ve answered on Shane’s question about builds that are queued but have no compatible agents.

I’ve also added your comment to this feature request. If this feature request is not exactly want you want (for example you want to get this list using REST API), please feel free to create new feature request in our tracker.

0
Comment actions Permalink

Thanks for the replies.

My question was *not* about queued builds.  As I tried to point out, that was the *one* way we were able to find them.

My question was about finding these builds proactively, so they could be fixed sooner, while the changes that caused the incompatibility were still fresh in the developers mind.

0

Please sign in to leave a comment.