Subversion Labeling failure

Hi there,

I get labeling errors, when I try to label my subversion project.

Doing the labeling by hand is no problem, but TeamCity gets an error.

My Labeling rulse is:
/trunk/fcm/mainapplication=>/tags/fcm/TeamCity

My labeling pattern is:
build-%system.build.number%

Doing it manually like this works fine:
svn cp -m "xx" http://.../trunk/fcm/mainapplication http://.../tags/fcm/TeamCity/build-23

Any Ideas?

And here is the error:

Labeling failed for root 'FMC root'
(see http://10.198.1.75:9080/TeamCity-4.5.2/viewLog.html?tab=buildChangesDiv&buildId=167&buildTypeId=bt6)
jetbrains.buildServer.vcs.VcsException: Labeling the path 'trunk/fcm/mainapplication' to 'tags/fcm/TeamCity/build-117' has failed with the error: svn: Cannot write to '/global/svn/repos/oss/db/transactions/573-i6.txn/node.0.0': /global/svn/repos/oss/db/transactions/573-i6.txn/node.0.0 (No such file or directory)
        at jetbrains.buildServer.buildTriggers.vcs.svn.SvnSupport.throwLabelingError(SvnSupport.java:513)
        at jetbrains.buildServer.buildTriggers.vcs.svn.SvnSupport.label(SvnSupport.java:501)
        at jetbrains.buildServer.vcs.impl.VcsLabeler.setLabel(VcsLabeler.java:68)
        at jetbrains.buildServer.vcs.impl.VcsLabeler.access$300(VcsLabeler.java:3)
        at jetbrains.buildServer.vcs.impl.VcsLabeler$3$1.run(VcsLabeler.java:3)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
Caused by: org.tmatesoft.svn.core.SVNException: svn: Cannot write to '/global/svn/repos/oss/db/transactions/573-i6.txn/node.0.0': /global/svn/repos/oss/db/transactions/573-i6.txn/node.0.0 (No such file or directory)
        at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:82)
        at org.tmatesoft.svn.core.internal.wc.SVNFileUtil.openFileForWriting(SVNFileUtil.java:1256)
        at org.tmatesoft.svn.core.internal.wc.SVNFileUtil.openFileForWriting(SVNFileUtil.java:1235)
        at org.tmatesoft.svn.core.internal.io.fs.FSFS.putTxnRevisionNode(FSFS.java:985)
        at org.tmatesoft.svn.core.internal.io.fs.FSFS.createNewTxnNodeRevisionFromRevision(FSFS.java:975)
        at org.tmatesoft.svn.core.internal.io.fs.FSTransactionRoot.createTxn(FSTransactionRoot.java:202)
        at org.tmatesoft.svn.core.internal.io.fs.FSTransactionRoot.beginTransaction(FSTransactionRoot.java:176)
        at org.tmatesoft.svn.core.internal.io.fs.FSTransactionRoot.beginTransactionForCommit(FSTransactionRoot.java:170)
        at org.tmatesoft.svn.core.internal.io.fs.FSCommitEditor.openRoot(FSCommitEditor.java:94)
        at org.tmatesoft.svn.core.internal.wc.SVNCommitUtil.driveCommitEditor(SVNCommitUtil.java:93)
        at jetbrains.buildServer.buildTriggers.vcs.svn.SvnCopyHelper.doCopy(SvnCopyHelper.java:102)
        at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection.label(SvnConnection.java:1130)
        at jetbrains.buildServer.buildTriggers.vcs.svn.SvnSupport.label(SvnSupport.java:499)
        ... 11 more
Caused by: java.io.FileNotFoundException: /global/svn/repos/oss/db/transactions/573-i6.txn/node.0.0 (No such file or directory)
        at java.io.FileOutputStream.open(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
        at org.tmatesoft.svn.core.internal.wc.SVNFileUtil.createFileOutputStream(SVNFileUtil.java:1266)
        at org.tmatesoft.svn.core.internal.wc.SVNFileUtil.openFileForWriting(SVNFileUtil.java:1252)
        ... 22 more

Thanks,
   Malte

1 comment
Comment actions Permalink

I found the problem myself.

It was due to file access rights.

TeamCity accessed the subversion via file:// url and didn't have the rights to change files

0

Please sign in to leave a comment.