Bugzilla Integration TC 5.0
I'm trying out 5.0, and I'm having trouble setting up the Bugzilla link. What is the url supposed to look like (i.e. http://server/bugs/bugzilla/showbug.cgi ) ? What is the issue id pattern (regex like (\d{4}) ) ? The documentation doesn't seem to have this information, but I have looked around in the forums.
When I try the above settings, I get "Error: Failed to read server's response: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/html4/loose.dtd" which seems to be very much like http://youtrack.jetbrains.net/issue/TW-9342
Thanks,
Jim
Please sign in to leave a comment.
Part success. If I take out my login information (bugzilla guest access is enabled), the test connection button works.
Jim,
Sorry for the delay. The question is still relevant? If yes please leave a comment or create a separate thread.
Kind regards,
Marina
Yes, this is still relevant. I can get it working, just only anonymously and I just tested it again. I'm on 5.0 (build 10669) . At some point I'll get around to upgrading, but TeamCity works so well right now (with the exception of the bugzilla integration) that I don't want to break it.
Hi Jim,
Do I understand correctly that the issue is with getting bugzilla integration work when credentials for the connection are provided?
What Bugzilla do you use?
Could you please create the connection and hover over any issue link. This most probably won't succeed, but should produce the error stacktrace in the log. I would appreciate if you attach it here.
---
Maxim
That is correct.
Bugzilla version 3.4.2
I must not have logging configured correctly, because I don't see anything logged for this problem. I have log4j configured for DEBUG level like this link http://confluence.jetbrains.net/display/TCD5/Reporting+Issues#ReportingIssues-LoggingEvents
What log should I be looking in, and what configuration file controls that log?
Hi Jim,
There is no logging in 5.0 for "Test connection" errors (fixed in 5.1.x), that's why I asked you to get the error the other way.
Try to create the connection and find the issue mention in commits comments (or build's comments). Getting the issue details should produce the error and this time it should be dumped into the log (teamcity-server.log if I'm not mistaken).
Or you can upgrade to 5.1.3 - there were few Bugzilla-related fixes, may be your problem is one of them.
---
Maxim