TeamCity Compatibility
wstrachan opened this issue · 4 comments
Do you know if there are any issues with the build monitor and TeamCity 2017.2.2 (build 50909)? I'm unable get my builds to display. Not sure if it's an authentication issue? I have my server configured for Basic HTTP authentication and I've successfully issued a GET to the server's API using the full URL for a specific configuration (see example below).
http://username:password@tc-server:8111/httpAuth/app/rest/buildTypes/id:_buildConfigurationId_
Am I missing anything? Perhaps a configuration on the TC server side? This app seems to be a perfect fit for what I'm looking for. It would be great to get it working.
Any assistance or advice would be greatly appreciated.
This is an example of my config:
{
"monitor": {
"interval": 5000,
"numberOfBuilds": 10,
"latestBuildOnly": false,
"sortOrder": "date",
"debug": true
},
"services": [
{
"name": "TeamCity",
"configuration": {
"url": "http://username:password@tc-server:8111",
"buildConfigurationId": "default_build",
"branch": "master"
}
}
]
}
And this the output when I run the app:
Printing environment Variables...
PORT = unset (Default: 3000)
NODE_TLS_REJECT_UNAUTHORIZED = unset (Default: 1)
node-build-monitor is starting...
11:38:21 AM | Check for builds...
node-build-monitor 0.9.44 is listening on port 3000...
11:38:21 AM | 0 builds found....
11:38:26 AM | Check for builds...
11:38:26 AM | 0 builds found....
11:38:31 AM | Check for builds...
11:38:31 AM | 0 builds found....
I'm sorry to say, that I'm not using a Team City instance.
Maybe you can debug into the code and provide a PR for that issue.
After more troubleshooting, it seems to only be an issue with certain builds and is most likely a problem with my TeamCity server.
Great app! Thanks!
Thank you. 😉