TC build 1681 ignoring "JDK home path" regression?

It appears that there is a regression in TeamCity build 1681: The "JDK home path" value entered in a project seems to be ignored. The exact same configuration worked fine with build 1641. TeamCity server and agent is running with JDK 1.5 and my project runs with JDK 1.4.

When a build is run, I get the following in buildAgent/logs/teamcity.log:

INFO - erver.agent.ant.AntBuildRunner - Use Ant home: /data/workspaces/nextfire/main/tools/ant
INFO - nt.runner.GenericProgramRunner - Running: /usr/java/j2sdk1.4.2_12/bin/java -Dbuild.working.dir=/data/workspaces/nextfire/main -Duser.name=wf -Demma.instrumentation.parameters=-ix -Test -Dbuild.number=5 -Dos.name=Linux -Dant.task.extensions=jetbrains.buildServer.agent.ant.EchoAntExtension,jetbrains.buildServer.agent.ant.CompilerAntExtension,jetbrains.buildServer.testng.TestNGTaskExtension,jetbrains.buildServer.coverage.AntCoverageAdapter, -Duser.language=en -Duser.country=US -Didea.build.server.buildType.id=bt1 -Didea.build.agent.port=9090 -Dos.version=2.6.9-11.ELsmp -Duser.timezone=America/New_York -Dfile.encoding=ANSI_X3.4-1968 -Dfile.separator=/ -Dagent.work.dir=/data/workspaces/nextfire -Dos.arch=i386 -Dagent.classpath=/opt/TeamCity/buildAgent/lib/commons-codec-1.3.jar:/opt/TeamCity/buildAgent/plugins/coveragePlugin/lib/buildServerCoverageAgent.jar:/opt/TeamCity/buildAgent/lib/utils.jar:/opt/TeamCity/buildAgent/plugins/ant/lib/ant-nodeps.jar:/opt/TeamCity/buildAgent/lib/buildServerCommonRuntime.jar:/opt/TeamCity/buildAgent/lib/xmlrpc-2.0.1.jar:/opt/TeamCity/buildAgent/plugins/antPlugin/lib/buildServerAntServerLogging.jar:/opt/TeamCity/buildAgent/lib/buildServerServerLogging.jar:/opt/TeamCity/buildAgent/lib/junit-3.8.1.jar:/opt/TeamCity/buildAgent/lib/nanocontainer-1.0-RC-1.jar:/opt/TeamCity/buildAgent/lib/xpp3_min-1.1.3.4.M.jar:/opt/TeamCity/buildAgent/plugins/idea/lib/emma.jar:/opt/TeamCity/buildAgent/lib/buildServerMessages.jar:/opt/TeamCity/buildAgent/lib/buildServerXmlRpcWrapper.jar:/opt/TeamCity/buildAgent/plugins/testNGPlugin/lib/testNGAntExtension.jar:/opt/TeamCity/buildAgent/lib/xstream-1.1.2.jar -Dsuccessful.build.number=45 -Duser.home=/net/janus.orange.us/home/wf -DJAVA_HOME_14=/usr/java/j2sdk1.4.2_12 -Didea.build.server.build.id=12 -Dant.home=/data/workspaces/nextfire/main/tools/ant -Dpath.separator=: -DJAVA_OPTS=-Dmodification.check.interval=3600 -classpath /data/workspaces/nextfire/main/tools/ant/lib/ant-launcher.jar org.apache.tools.ant.launch.Launcher -v -Dwf.home=/data/workspaces/nextfire/main/core/output/dist/wf.home -Dwf.var=/data/workspaces/data/workspaces/nextfire/main/core/output/dist/wf.var -Doffline=true -lib /opt/TeamCity/buildAgent/lib/buildServerRuntimeUtil.jar:/opt/TeamCity/buildAgent/lib/junit-3.8.1.jar:/opt/TeamCity/buildAgent/plugins/antPlugin/lib/buildServerAntRunntime.jar -listener jetbrains.buildServer.agent.ant.AgentBuildListener -buildfile /data/workspaces/nextfire/main/build/teamcity-build.xml autobuild
INFO - nt.runner.GenericProgramRunner - /usr/java/j2sdk1.4.2_12/bin/java -Dbuild.working.dir=/data/workspaces/nextfire/main -Duser.name=wf -Demma.instrumentation.parameters=-ix -Test -Dbuild.number=5 -Dos.name=Linux -Dant.task.extensions=jetbrains.buildServer.agent.ant.EchoAntExtension,jetbrains.buildServer.agent.ant.CompilerAntExtension,jetbrains.buildServer.testng.TestNGTaskExtension,jetbrains.buildServer.coverage.AntCoverageAdapter, -Duser.language=en -Duser.country=US -Didea.build.server.buildType.id=bt1 -Didea.build.agent.port=9090 -Dos.version=2.6.9-11.ELsmp -Duser.timezone=America/New_York -Dfile.encoding=ANSI_X3.4-1968 -Dfile.separator=/ -Dagent.work.dir=/data/workspaces/nextfire -Dos.arch=i386 -Dagent.classpath=/opt/TeamCity/buildAgent/lib/commons-codec-1.3.jar:/opt/TeamCity/buildAgent/plugins/coveragePlugin/lib/buildServerCoverageAgent.jar:/opt/TeamCity/buildAgent/lib/utils.jar:/opt/TeamCity/buildAgent/plugins/ant/lib/ant-nodeps.jar:/opt/TeamCity/buildAgent/lib/buildServerCommonRuntime.jar:/opt/TeamCity/buildAgent/lib/xmlrpc-2.0.1.jar:/opt/TeamCity/buildAgent/plugins/antPlugin/lib/buildServerAntServerLogging.jar:/opt/TeamCity/buildAgent/lib/buildServerServerLogging.jar:/opt/TeamCity/buildAgent/lib/junit-3.8.1.jar:/opt/TeamCity/buildAgent/lib/nanocontainer-1.0-RC-1.jar:/opt/TeamCity/buildAgent/lib/xpp3_min-1.1.3.4.M.jar:/opt/TeamCity/buildAgent/plugins/idea/lib/emma.jar:/opt/TeamCity/buildAgent/lib/buildServerMessages.jar:/opt/TeamCity/buildAgent/lib/buildServerXmlRpcWrapper.jar:/opt/TeamCity/buildAgent/plugins/testNGPlugin/lib/testNGAntExtension.jar:/opt/TeamCity/buildAgent/lib/xstream-1.1.2.jar -Dsuccessful.build.number=45 -Duser.home=/net/janus.orange.us/home/wf -DJAVA_HOME_14=/usr/java/j2sdk1.4.2_12 -Didea.build.server.build.id=12 -Dant.home=/data/workspaces/nextfire/main/tools/ant -Dpath.separator=: -DJAVA_OPTS=-Dmodification.check.interval=3600 -classpath /data/workspaces/nextfire/main/tools/ant/lib/ant-launcher.jar org.apache.tools.ant.launch.Launcher -v -Dwf.home=/data/workspaces/nextfire/main/core/output/dist/wf.home -Dwf.var=/data/workspaces/data/workspaces/nextfire/main/core/output/dist/wf.var -Doffline=true -lib /opt/TeamCity/buildAgent/lib/buildServerRuntimeUtil.jar:/opt/TeamCity/buildAgent/lib/junit-3.8.1.jar:/opt/TeamCity/buildAgent/plugins/antPlugin/lib/buildServerAntRunntime.jar -listener jetbrains.buildServer.agent.ant.AgentBuildListener -buildfile /data/workspaces/nextfire/main/build/teamcity-build.xml autobuild

INFO - nt.runner.GenericProgramRunner - Apache Ant version 1.6.5 compiled on June 2 2005

INFO - nt.runner.GenericProgramRunner - Buildfile: /data/workspaces/nextfire/main/build/teamcity-build.xml

INFO - nt.runner.GenericProgramRunner - java.lang.UnsupportedClassVersionError: jetbrains/buildServer/testng/TestNGTaskExtension (Unsupported major.minor version 49.0)

9 comments
Comment actions Permalink

I'm seeing this, too. I had to back out to the released 1.0 version of TeamCity.

We seem to be seeing a number of issues regarding JDK 1.4 compatibility in TeamCity. It's pretty obvious that not enough testing is going on for 1.4 apps before new versions are released. As my group is still mostly on 1.4, that means that we'll have to test each new release before making it generally available. Sigh...


Douglas Bullard

0
Comment actions Permalink

I'm seeing this, too. I had to back out to the released 1.0 version of TeamCity.


I had to roll back to build 1654 as well after wasting 1/2 a day debugging this problem. Since I am not the only one experiencing this problem, I filed a new bug for this issue (TW-995).

We seem to be seeing a number of issues regarding JDK 1.4 compatibility in TeamCity. It's pretty obvious that not enough testing is going on for 1.4 apps before
new versions are released. As my group is still mostly on 1.4, that means that we'll have to test each new release before making it generally available. Sigh...


Agreed.

-Dave

0
Comment actions Permalink

Dave Leskovac wrote:
>> I'm seeing this, too. I had to back out to the released 1.0 version of TeamCity.


I had to roll back to build 1654 as well after wasting 1/2 a day debugging this problem. Since I am not the only one experiencing this problem, I filed a new bug for this issue (TW-995).

>> We seem to be seeing a number of issues regarding JDK 1.4 compatibility in TeamCity. It's pretty obvious that not enough testing is going on for 1.4 apps before
>> new versions are released. As my group is still mostly on 1.4, that means that we'll have to test each new release before making it generally available. Sigh...


I guess this is not a problem of JDK1.4.
Will take a look on what happened with JDK home path option.

KIR



--
Kirill Maximov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Kirill Maximov (JetBrains) wrote:

Dave Leskovac wrote:

>>> I'm seeing this, too. I had to back out to the released 1.0 version
>>> of TeamCity.
>>
>> I had to roll back to build 1654 as well after wasting 1/2 a day
>> debugging this problem. Since I am not the only one experiencing this
>> problem, I filed a new bug for this issue (TW-995).
>>
>>> We seem to be seeing a number of issues regarding JDK 1.4
>>> compatibility in TeamCity. It's pretty obvious that not enough
>>> testing is going on for 1.4 apps before new versions are released.
>>> As my group is still mostly on 1.4, that means that we'll have to
>>> test each new release before making it generally available. Sigh...
>>


I guess this is not a problem of JDK1.4.
Will take a look on what happened with JDK home path option.


I've just checked - this option works for me (at least it allows to use
jdk 1.4 for running ant runner).

Which runner do you use? Can you provide build agent logs?


KIR




--
Kirill Maximov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Kirill Maximov (JetBrains) wrote:
I've just checked - this option works for me (at
least it allows to use
jdk 1.4 for running ant runner).
Which runner do you use? Can you provide build
agent logs?

Hi Kir,

I will send you the logs as an email attachment.

Thanks,
-Dave

0
Comment actions Permalink

Dave Leskovac wrote:
>> Kirill Maximov (JetBrains) wrote:
>> I've just checked - this option works for me (at
>> least it allows to use
>> jdk 1.4 for running ant runner).
>> Which runner do you use? Can you provide build
>> agent logs?

Hi Kir,

I will send you the logs as an email attachment.


Got it. Please watch
http://www.jetbrains.net/jira/browse/TW-1004 .

As a workaround please remove buildAgent/plugins/testng directory on build agent.


Thanks,
-Dave



--
Kirill Maximov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

As a workaround please remove buildAgent/plugins/testng directory on build agent.


Just so I am clear on this, should the following be removed?:
buildAgent/plugins/testNGPlugin/
buildAgent/plugins/testNGPlugin.zip

Thanks,
-Dave

0
Comment actions Permalink

Dave Leskovac wrote:
>> As a workaround please remove buildAgent/plugins/testng directory on build agent.


Just so I am clear on this, should the following be removed?:
buildAgent/plugins/testNGPlugin/
buildAgent/plugins/testNGPlugin.zip


I'd suggest do not touch testNGPlugin.zip but remove only testNGPlugin directory.
Otherwise agent will be upgraded from server upon a restart.


Thanks,
-Dave



--
Kirill Maximov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Dave Leskovac wrote:
>> As a workaround please remove
buildAgent/plugins/testng directory on build agent.


Just so I am clear on this, should the following be

removed?:

buildAgent/plugins/testNGPlugin/
buildAgent/plugins/testNGPlugin.zip


I'd suggest do not touch testNGPlugin.zip but
remove only testNGPlugin directory.
Otherwise agent will be upgraded from server upon a
restart.


Okay. After removing the buildAgent/plugins/testNGPlugin/ directory, I can once again successfully specify JDK 1.4.2 in the build agent using TC build 1681.

Thanks, Kir!

-Dave

0

Please sign in to leave a comment.