Problem with SVN working copy using buildnumber-maven-plugin

Hi,

I've recently introduced the buildnumber-maven-plugin in our Maven build.

I'm facing a problem that can be easily resumed with the following  failed build log:


[06:45:42] Clean build enabled: removing old files from /usr/local/buildAgent/work/c553c77398338b70
[06:45:42] Clearing temporary directory: /usr/local/buildAgent/temp/buildTmp
[06:45:42] Checkout directory: /usr/local/buildAgent/work/c553c77398338b70
[06:45:50] Loading changed files from server...
[06:46:21] MAVEN_OPTS = -server -Xmx512m -XX:MaxPermSize=256m -Dteamcity.buildType.id=bt3 -Dteamcity.build.properties.file=/usr/local/buildAgent/temp/agentTmp/teamcity.build63527.properties -Dbuild.number=175 -Dagent.home.dir=/usr/local/buildAgent -Dteamcity.idea.home=/usr/local/buildAgent/plugins/idea -Dagent.work.dir=/usr/local/buildAgent/work -Dagent.name=ALLENCESRV03 -Dteamcity.build.workingDir=/usr/local/buildAgent/work/c553c77398338b70 -Dteamcity.build.checkoutDir=/usr/local/buildAgent/work/c553c77398338b70 -Duser.home=/root -Djava.io.tmpdir=/usr/local/buildAgent/temp/buildTmp -Dfile.separator=/ -Dagent.flow=3612884236837111 -Dbuild.vcs.number.1=3129 -Dfile.encoding=UTF-8 -Dteamcity.projectName=alpha2 -Didea.build.agent.port=9091 -Dteamcity.auth.userId=TeamCityBuildId=608 -Dteamcity.auth.password=q5ePrUVwAYgCSfQQAEpcZh5hVwr18wdZ -Didea.build.server.build.id=608 -Duser.timezone=Europe/Paris -Dos.name=Linux -Dteamcity.agent.cpuBenchmark=412 -Dpath.separator=: -Dos.version=2.6.27-9-generic -Dteamcity.build.tempDir=/usr/local/buildAgent/temp/buildTmp -Dbuild.vcs.number.alpha2=3129 -Duser.language=en -Dos.arch=i386 -Duser.name=root -Dbuild.number.format={0} -Duser.country=US -Dbuild.vcs.number=3129
[06:46:21] M2_HOME = /opt/local/maven
[06:46:21] PATH = /opt/local/maven/bin:/opt/local/maven/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
[06:46:21] JAVA_HOME = /usr/lib/jvm/java-6-sun-1.6.0.10
[06:46:22] [INFO] Scanning for projects...
[06:46:22] [INFO] ------------------------------------------------------------------------
[06:46:22] [INFO] Building alpha2
[06:46:22] [INFO]    task-segment: [package]
[06:46:22] [INFO] ------------------------------------------------------------------------
[06:46:23] [WARNING] Attempting to build MavenProject instance for Artifact (org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-3-20090414.214556-8) of type: maven-plugin; constructing POM artifact instead.
[06:46:25] Downloading: http://allence:8081/artifactory/repo/net/java/dev/jna/jna/3.0.5/jna-3.0.5.pom
[06:46:26] Downloading: http://allence:8081/artifactory/repo/net/java/dev/jna/jna/3.0.5/jna-3.0.5.pom
[06:46:27] [INFO] [buildnumber:create {execution: default}]
[06:46:27] [INFO] Change the default 'svn' provider implementation to 'javasvn'.
[06:46:27] [INFO] Checking for local modifications: skipped.
[06:46:27] [INFO] Updating project files from SCM: skipped.
[06:46:27] [INFO] ------------------------------------------------------------------------
[06:46:27] [ERROR] BUILD ERROR
[06:46:27] [INFO] ------------------------------------------------------------------------
[06:46:27] [INFO] Cannot get the revision information from the scm repository :
[06:46:27] Exception while executing SCM command.
[06:46:27] svn: '/usr/local/buildAgent/work/c553c77398338b70' is not a working copy

The local check out of the project doesn't seem to be an SVN working copy and as such the buildumber plugin can't invoke a 'svn info' on the local copy.
This is all the plugin needs to figure the SVN revision.
I'll have to disable the plugin for the TeamCity build, but I'd like to understand why the local check out (is it actually an SVN check out?) isn't considered as a working copy??

thanks
-nodje



1 comment
Comment actions Permalink

You should change checkout mode on the VCS settings page of your build configuration to "Automatically on agent".

0

Please sign in to leave a comment.