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
Can't connect to TeamCity server since it was upgraded to 8.x #24
Comments
|
I'm looking into this now Damian. FYI in general you can hit that little yellow triangle to get more detail, but no need in this case since, if like you say they changed the REST API surface, that will require me to do some digging anyway. |
|
Hey Damian, Siren of Shame 2.1.3 is connecting successfully to a fresh installation of TeamCity 8 for me. It's reading successful and failed build states. Can you please provide error logs? There's an older screenshot on our blog that shows how to get them: http://sirenofshame.blogspot.com/2012/01/how-to-report-errors.html. Thanks, |
|
Just tried again and still not working. Here is the log: 2014-01-01 10:56:10,904 [1] INFO SirenOfShame.Lib.MyLogManager [(null)] - Logging configured Error has occurred during request processing (Not Found). |
|
OK I think I figured it out. A build configuration had been deleted and thus a 404 was being thrown which isn't being handled nicely by SOS. I changed the SOS configuration to monitor the existing build configurations and now it's fine. Might want to look at how you deal with build configurations being deleted. |
…d as server unavailable. Addresses Issue #24.
We upgraded our TeamCity server to 8.x from 7.x and now SOS can't update build status. Error message is shown in status bar:
The configure screen is able to connect OK and list the projects and build configurations:
TeamCity changed it's REST API surface in 8.x so it's possible the issue is caused by that.
The text was updated successfully, but these errors were encountered: