TeamCity service only supports individual build configs, not projects.

[lochsh]

On TeamCity, build configurations can be organised into projects. We can get information about the project, including it's status (e.g. SUCCESS or FAILURE) using this API call:

https:/teamcity-server/app/rest/projects/ProjectID

The project status is SUCCESS if all of the build configurations in the project are passing.

For large projects, it can be quite limiting to have node-build-monitor only support individual build configs. For us, there is only so much space on our CI status board (displayed on a wall-mounted TV in the office), and not enough space to show every single build configuration. Being able to show the status of a project would be very helpful for this reason.

I'm not sure the best way to achieve this. Perhaps we can try sending a request for a build config, and if it fails, try sending a request for a project with the same ID. Or, the config.json file could change so that each configuration has a boolean flag for whether it is a project.

The response from querying a project rather than an individual build config will have some different fields, so this would also need to be taken into account.

[marcells]

You can write a custom theme for the build monitor. Could this help you for the space problem?

If it doesn't help, then I would recommend to create another service (e.g. TeamCityProjectsOverview.js), which lists the whole project status instead of build status. Mixing it with the current service makes it too complicate, cause that are different use cases.

Can all properties (id, project, definition, number, isRunning, startedAt, finishedAt, requestedFor, statusText, status, reason, hasErrors, hasWarnings, url), which are needed by the frontend be filled with senseful values?