-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TeamCity service doesn't show if build configurations are paused #73
Comments
Hey @lochsh, originally the build monitor was intended to show builds. If I understand you correctly, the build itself isn't paused, but the configuration is. So, the gray color could be misleading and will affect all builds belonging to the configuration. Maybe you could write another service (e.g. TeamCityConfigurations.js) to list all configurations and their state. Feel free to make a PR. ;-) |
Thanks for getting back to me @marcells, I've been on holiday so sorry for the late response! |
It would be useful to have an indication of whether a TeamCity build configuration is paused (i.e. all triggers have been disabled, so the CI test isn't currently active).
If a test passes and is then paused for a long time, it can be misleading for the build monitor to show it as successful.
The TeamCity service gets information about specific builds in time, which doesn't give us any information about whether the build configuration they belong to is paused. However, we can find out whether the build config is paused with this API call:
https://teamcity-server/app/rest/buildTypes/id:BuildConfigurationId/paused
Perhaps the grey colour can be used to indicate a paused config, as well as a cancelled build.
The text was updated successfully, but these errors were encountered: