TW-1279 |
"Problems with VCS connection: can not get project sources" |
|
0
|
|
There must be a long comment or something, but my builds all have the same error message with the same details - "column truncated"
Looking in the SVN history shows that the last commit has a comment with a length of 284 characters.
Issue wasresolved
Looking in the SVN history shows that the last commit has a comment with a length of 284 characters.
Issue wasresolved
|
Gibson 01 Dec 2006 21:03 (2 years ago) |
Relevant part of teamcity-vcs attached. It seems that the "500 Internal server error" isn't serious, but the "Data truncation" is ...
|
|
|
Gibson 01 Dec 2006 21:06 (2 years ago) |
Subsequent to this problem, builds that are supposed to trigger on VCS commit have to be launched manually.
|
|
|
Gibson 04 Dec 2006 11:39 (2 years ago) |
Actually, nothing is getting checked out at all, the manually launched builds just build with 0 changes (so I suppose they're building from the revision before the server got "stuck")
|
|
|
Gibson 04 Dec 2006 11:49 (2 years ago) |
Forgot to mention, I'm using MySQL as my underlying DB.
|
|
|
Gibson 04 Dec 2006 12:34 (2 years ago) |
I worked around this by widening the relevant column, but it is TeamCity's responsibility to make sure data that is being written fits into the given column/table. I don't mind if that column is truncated (it's not TeamCity's responsibility to keep a complete version history, I have my Subversion server for that), but obviously it shouldn't crash in this case.
|