Eclipse plugin

We are trying to use the Eclipse plugin to test out the "personal build" feature, and we're having trouble getting the code to commit after the tests have run successfully.  The tests all run successfully, and we get the confirmation message asking for confirmation before committing the code.  When we click on yes to commit the code, this is the error message that we get:

!ENTRY jetbrains.teamcity.core 4 0 2009-01-06 09:27:44.521
!MESSAGE svn: Commit failed (details follow):
svn: CHECKOUT of '/svn-repositories/Development/!svn/ver/4932/PocProject/src/main/java/ca/foo/App.java': 403 Forbidden (http://svnserver)
!STACK 1
org.eclipse.core.runtime.CoreException: svn: Commit failed (details follow):
svn: CHECKOUT of '/svn-repositories/Development/!svn/ver/4932/PocProject/src/main/java/ca/foo/App.java': 403 Forbidden (http://svnserver)
    at jetbrains.teamcity.vcs.svn.SVNSubscriber$3.run(SVNSubscriber.java:313)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782)
    at jetbrains.teamcity.vcs.svn.SVNSubscriber.doDelayedCommit(SVNSubscriber.java:288)
    at jetbrains.teamcity.core.remote.VCSManager.doDelayedCommit(VCSManager.java:457)
    at jetbrains.teamcity.core.remote.RemoteRunManager2$2$1.run(RemoteRunManager2.java:154)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782)
    at jetbrains.teamcity.core.remote.RemoteRunManager2$2.run(RemoteRunManager2.java:152)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 jetbrains.teamcity.core 4 4 2009-01-06 09:27:44.521
!MESSAGE svn: Commit failed (details follow):
svn: CHECKOUT of '/svn-repositories/Development/!svn/ver/4932/PocProject/src/main/java/ca/foo/App.java': 403 Forbidden (http://svnserver)

From what I have read, it seems like when you use this feature to check in the code after the tests are successful that it should be doing the checkin from the machine that made the request, using the SVN credentials that are cached on that machine.  However, I've never seen an error like this on my machine before, and I have no trouble committing this code through subclipse.  We currently have the professional edition of TeamCity.  Is it possible that this version might be causing the problem?

Has anyone else seen this error message before?  Does anyone have any suggestions for what might be the problem?

4 comments

The "403 Forbidden" error for SVN is common trouble. There is an article describes a similar case and can help you to solve the issue:
http://www.alagad.com/go/blog-entry/subversion-mkactivity-and-403-forbidden-headaches

BR,
Konstantin

0

Thanks for the info.  Unfortunately, I had already read this blog, and I didn't find anything that will help us out.  It pretty much talks about problems while committing to SVN, but if you look carefully at the stacktrace, it is actually saying that it's having trouble checking out.  Also, this blog talks about case issues, which are not present in our case.  The url is actually correct - including the case of each letter.  And, I can check out an commit to my heart's desire on my computer - just not through TeamCity. It seems like TeamCity is trying to check out a particular revision before the commit.  Whatever it does, something isn't quite jiving with our system.   Is there anything different that TeamCity does when it attempts to do the commit?  Does it manipulate the url or user id on my machine before trying the commit?

0

The plugin does not manipulate neither url nor user id just uses cached by SVNKit user's credentials(SNNKIt is only library the plugin uses for SVN interaction). So you can try:
1. remove cached one and login again over the next attempt of DelayedCommit. The SVNKit stores a credentials into <your_eclipse_home>/configuration/org.eclipse.core.runtime/.keyring file.
2. check support SVN server of SVNKit. Set a connector of your Eclipse's Team Provider to SVNKit(Preferences/SVN/SVN Connector) and try to commit problem file trought build-in Eclipse's team action.

BR,
Konstantin

0

It looks like there is a problem with SVNKit.  I'm currently investigating it (with no luck so far), but I believe that once we've got that figured out the TeamCity plugin will work.

Thanks very much for your help!

0

Please sign in to leave a comment.