Setting JDK for a build configuration

Hello,

I am prototyping TeamCity for my company. I have used CruiseControl in the past and am running into certain issues with TC - some of which have been fixed by the latest public beta (1529). This is my first post to this forum and I will post issue by issue.

I am confused by the behavior of the UI's "JDK home path:" field within a build configuration.
The environment's JAVA_HOME is set like this:
JAVA_HOME=/usr/java/jdk1.5.0_08.
The buildAgent.properties file contains this setting:
env.JAVA_HOME=/usr/java/jdk1.5.0_08.

I set the "JDK home path:" field within a build configuration to this:
/usr/java/j2sdk1.4.2.12

This was done because my build needs to use JDK1.4.2. Once that value was set in the UI, the agent gives this error:
java.lang.UnsupportedClassVersionError: jetbrains/buildServer/coverage/AntCoverageAdapter (Unsupported major.minor version 49.0).
After removing that value from the UI, the build proceeded.

This indicates to me that the value within the build configuration affects the agent as well as or instead of the actual build. (I don't know if the JDK affects the build yet as I have not had a successful build so far). Is this known behavior? Is this a bug?

Thanks,
-Dave

2 comments
Comment actions Permalink

This indicates to me that the value within the build configuration affects the agent as well as or instead of the actual build. (I
don't know if the JDK affects the build yet as I have not had a successful build so far). Is this known behavior? Is this a bug?


The value set in the build configuration has priority over the value that is set locally on the agent machine, so this is expected
behaviour.


As for the exception, this is covered by the issue

http://www.jetbrains.net/jira/browse/TW-688

which has already been fixed and the fix will be available in the coming EA version.
Please see issue comments for the workaround


--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"



0
Comment actions Permalink

Applying the TW-688 workaround fixed my problem. Thanks for the quick response.

-Dave

0

Please sign in to leave a comment.