Checkout but no build?

I'm attempting to do a checkout and build. I think I got the checkout working (mostly with some road bumps) but it doesn't seem to call the ant task or give any errors about trying to call an ant task. Here's my project segment (modified slightly for security):

]]>

Also, it would be nice if the log messages used normal timestamps. Right now it shows like:

INFO - l.XmlConfigurationExternalizer - Will keep messages for 10 days but not less than 30 builds10 days for CodeHaus_XStream

Thanks,
Steve

25 comments
Comment actions Permalink

You have to specify 'build-file' property it you're sending the build file
content.
In order to specify file on the agent computer use 'build-file-path'.

"Steve Wardell" <no_reply@jetbrains.com> wrote in message
news:18483998.1144959181487.JavaMail.itn@is.intellij.net...

I'm attempting to do a checkout and build. I think I got the checkout
working (mostly with some road bumps) but it doesn't seem to call the ant
task or give any errors about trying to call an ant task. Here's my
project segment (modified slightly for security):

>

<project name="Trunk">
<vcs-roots>
<vcs-root type="svn">
<param name="url"
value="svn+ssh://svn.office/data/svn/src/project1/trunk"/>
<param name="user" value="username"/>
<param name="password" value="password"/>
<param name="checkout-root" value="project1"/>
</vcs-root>

>

<vcs-root type="svn">
<param name="url"
value="svn+ssh://svn.office/data/svn/src/project2/trunk"/>
<param name="user" value="username"/>
<param name="password" value="password"/>
<param name="checkout-root" value="project2"/>
</vcs-root>
</vcs-roots>

>

<build-type name="Trunk" run-type="Ant" checkout-on-server="true"
id="Trunk_ID">
<run-parameters>
<param name="build-file"
value="%build.working.dir%/project1/build.xml"/>
<param name="target" value="Dev_Build"/>
</run-parameters>
<parameters>
<param name="project2.root" value="%build.working.dir%/project2"/>
<param name="jdk.home" value="/usr/java/jdk"/>
<param name="jwsdp.home" value="/usr/java/jwsdp-1.5"/>
</parameters>

>

<notification-set>
<notificator type="email"/>
</notification-set>

>
>

<keep what="messages" days="10" builds="10"/>
</build-type>
</project>

>

Also, it would be nice if the log messages used normal timestamps. Right
now it shows like:

>

INFO - l.XmlConfigurationExternalizer - Will keep messages for
10 days but not less than 30 builds10 days for CodeHaus_XStream

>

Thanks,
Steve



0
Comment actions Permalink

I'm not clear on the change that I need to make. I changed build-file to build-file-path as shown below but received the same results of no build occurring. Was that the change I was supposed to make or a different change? If you could clarify that would be great.

Thanks,
Steve

]]>

0
Comment actions Permalink

Looks like the configuration has to work.

Could you please activate logging for the build agent (just uncomment block
--> in agent_dist/bin/log4j.xml file ), restart agent and attach console output? "Steve Wardell" ]]> wrote in message
news:7817168.1145308142038.JavaMail.itn@is.intellij.net...

I'm not clear on the change that I need to make. I changed build-file to
build-file-path as shown below but received the same results of no build
occurring. Was that the change I was supposed to make or a different
change? If you could clarify that would be great.

>

Thanks,
Steve

>

<build-type name="Trunk" run-type="Ant" checkout-on-server="true"
id="Trunk_ID">
<run-parameters>
<param name="build-file-path"
value="%build.working.dir%/build.xml"/>
<param name="target" value="Dev_Build"/>
</run-parameters>
<parameters>
<param name="interface.root"
value="%build.working.dir%/interface"/>
<param name="jdk.home" value="/usr/java/jdk"/>
<param name="jwsdp.home" value="/usr/java/jwsdp-1.5"/>
</parameters>

>

<notification-set>
<notificator type="email"/>
</notification-set>

>

<keep what="messages" days="10" builds="10"/>
</build-type>



0
Comment actions Permalink

Here's the log entries I see (I changed the IP and hostname for security reasons):

INFO - brains.buildServer.NetworkUtil - Found Network Interfaces:
INFO - r.agent.impl.ServerXmlRpcProxy - Registering on build server: Agent hostnane.com 192.168.1.10 9090 [, , ]]>]
INFO - rver.agent.impl.BuildAgentImpl - Applying patch...
INFO - rver.agent.impl.BuildAgentImpl - Patch applied in 8 seconds
INFO - erver.agent.ant.AntBuildRunner - Runtime classpath:
/usr/local/buildAgent/lib/buildServerMessages.jar
/usr/local/buildAgent/lib/commons-codec-1.3.jar
/usr/local/buildAgent/lib/xpp3_min-1.1.3.4.M.jar
/usr/local/buildAgent/lib/buildServerXmlRpcWrapper.jar
/usr/local/buildAgent/plugins/antPlugin/lib/buildServerAntServerLogging.jar
/usr/local/buildAgent/lib/nanocontainer-1.0-RC-1.jar
/usr/local/buildAgent/lib/xmlrpc-2.0.jar
/usr/local/buildAgent/lib/buildServerRuntimeUtil.jar
/usr/local/buildAgent/plugins/ant/lib/ant-nodeps.jar
/usr/local/buildAgent/lib/buildServerCommonRuntime.jar
/usr/local/buildAgent/lib/xstream-1.1.2.jar
INFO - erver.agent.ant.AntBuildRunner - Ant working directory: /usr/local/buildAgent/work/Trunk

0
Comment actions Permalink

Any further thoughts on the issue or data I could provide to help diagnose this? I'm kind of at a standstill as a result.

Thanks,
Steve

0
Comment actions Permalink

Hi Steve,

Please try to replace INFO with DEBUG in the section

]]>

Sorry for the silence, Olesya is out of the office for a week.

With kind regards,
KIR

0
Comment actions Permalink

That helped get more useful data. Here's the new log data (I'm not seeing as a way to attach the file to this message so sorry for the long paste):

INFO - erver.agent.ant.AntBuildRunner - Ant working directory: /usr/local/buildAgent/work/Trunk
DEBUG - erver.agent.ant.AntBuildRunner - java -Didea.build.server.build.id=96 -Didea.build.server.buildType.id=Trunk_ID -Didea.build.agent.port=9090 -Dbuild.working.dir=/usr/local/buildAgent/work/Trunk -Dant.home=/usr/local/buildAgent/bin/../plugins/ant -Dagent.work.dir=/usr/local/buildAgent/work -Dagent.classpath=/usr/local/buildAgent/lib/buildServerMessages.jar:/usr/local/buildAgent/lib/commons-codec-1.3.jar:/usr/local/buildAgent/lib/xpp3_min-1.1.3.4.M.jar:/usr/local/buildAgent/lib/buildServerXmlRpcWrapper.jar:/usr/local/buildAgent/plugins/antPlugin/lib/buildServerAntServerLogging.jar:/usr/local/buildAgent/lib/nanocontainer-1.0-RC-1.jar:/usr/local/buildAgent/lib/xmlrpc-2.0.jar:/usr/local/buildAgent/lib/buildServerRuntimeUtil.jar:/usr/local/buildAgent/plugins/ant/lib/ant-nodeps.jar:/usr/local/buildAgent/lib/buildServerCommonRuntime.jar:/usr/local/buildAgent/lib/xstream-1.1.2.jar -Dant.task.extensions=jetbrains.buildServer.agent.ant.CompilerAntExtension, -Dnext.successful.build.id=20 -Dnext.build.id=30 -classpath /usr/local/buildAgent/bin/../plugins/ant/lib/ant-launcher.jar org.apache.tools.ant.launch.Launcher -lib /usr/local/buildAgent/lib/junit-3.8.1.jar:/usr/local/buildAgent/lib/buildServerRuntimeUtil.jar:/usr/local/buildAgent/plugins/antPlugin/lib/buildServerAntRunntime.jar -listener jetbrains.buildServer.agent.ant.AgentBuildListener -buildfile /usr/local/buildAgent/work/Trunk/build.xml Banter_Dev_Build

DEBUG - erver.agent.ant.AntBuildRunner - Buildfile: /usr/local/buildAgent/work/Trunk/build.xml

DEBUG - erver.agent.impl.ServerMonitor - Agent ping from server
DEBUG - erver.agent.ant.AntBuildRunner -

DEBUG - erver.agent.ant.AntBuildRunner - BUILD FAILED

DEBUG - erver.agent.ant.AntBuildRunner - java.lang.NoClassDefFoundError: jetbrains.buildServer.messages.BlockMessage

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.Class.initializeClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at jetbrains.buildServer.agent.ant.ServerLoggerFacade.activityStarted (ServerLoggerFacade.java:78)

DEBUG - erver.agent.ant.AntBuildRunner - at jetbrains.buildServer.agent.ant.AgentBuildListener.taskStarted (AgentBuildListener.java:155)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.Project.fireTaskStarted (Project.java:1938)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.Task.perform (Task.java:361)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.Target.execute (Target.java:341)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.helper.ProjectHelper2.parse (ProjectHelper2.java:144)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.ProjectHelper.configureProject (ProjectHelper.java:92)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.Main.runBuild (Main.java:655)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.Main.startAnt (Main.java:188)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.launch.Launcher.run (Launcher.java:247)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.launch.Launcher.main (Launcher.java:68)
DEBUG - erver.agent.ant.AntBuildRunner - Caused by: java.lang.ClassNotFoundException: java.lang.Enum not found in jetbrains.buildServer.agent.ant.AgentClassLoader{urls=[file:/usr/local/buildAgent/lib/buildServerMessages.jar,file:/usr/local/buildAgent/lib/commons-codec-1.3.jar,file:/usr/local/buildAgent/lib/xpp3_min-1.1.3.4.M.jar,file:/usr/local/buildAgent/lib/buildServerXmlRpcWrapper.jar,file:/usr/local/buildAgent/plugins/antPlugin/lib/buildServerAntServerLogging.jar,file:/usr/local/buildAgent/lib/nanocontainer-1.0-RC-1.jar,file:/usr/local/buildAgent/lib/xmlrpc-2.0.jar,file:/usr/local/buildAgent/lib/buildServerRuntimeUtil.jar,file:/usr/local/buildAgent/plugins/ant/lib/ant-nodeps.jar,file:/usr/local/buildAgent/lib/buildServerCommonRuntime.jar,file:/usr/local/buildAgent/lib/xstream-1.1.2.jar], parent=java.net.URLClassLoader{urls=[file:/usr/local/buildAgent/lib/junit-3.8.1.jar,file:/usr/local/buildAgent/lib/buildServerRuntimeUtil.jar,file:/usr/local/buildAgent/plugins/antPlugin/lib/buildServerAntRunntime.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-vaj.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-weblogic.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-netrexx.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-apache-bsf.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-icontract.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-apache-log4j.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-stylebook.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-xalan1.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-starteam.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-apache-oro.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-junit.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/xercesImpl.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-apache-resolver.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-jsch.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-jmf.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-commons-logging.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-xslp.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/xml-apis.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-apache-bcel.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-swing.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-jai.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-trax.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-commons-net.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-nodeps.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-apache-regexp.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-antlr.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-launcher.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-javamail.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/junit.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-jdepend.jar,file:/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/lib/tools.jar], parent=gnu.gcj.runtime.SystemClassLoader{urls=[file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-launcher.jar], parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}}}

DEBUG - erver.agent.ant.AntBuildRunner - at java.net.URLClassLoader.findClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.ClassLoader.loadClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at jetbrains.buildServer.agent.ant.AgentClassLoader.loadClass (AgentClassLoader.java:28)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.ClassLoader.loadClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.VMClassLoader.defineClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.ClassLoader.defineClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.security.SecureClassLoader.defineClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.net.URLClassLoader.findClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.ClassLoader.loadClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at jetbrains.buildServer.agent.ant.AgentClassLoader.loadClass (AgentClassLoader.java:28)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.ClassLoader.loadClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.Class.forName (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.Class.initializeClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - ...11 more

DEBUG - erver.agent.ant.AntBuildRunner -

DEBUG - erver.agent.ant.AntBuildRunner - Total time: 1 second

DEBUG - erver.agent.ant.AntBuildRunner - java.lang.NoClassDefFoundError: jetbrains.buildServer.messages.TextMessage

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.Class.initializeClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at jetbrains.buildServer.agent.ant.ServerLoggerFacade.error (ServerLoggerFacade.java:111)

DEBUG - erver.agent.ant.AntBuildRunner - at jetbrains.buildServer.agent.ant.AgentBuildListener.processException (AgentBuildListener.java:100)

DEBUG - erver.agent.ant.AntBuildRunner - at jetbrains.buildServer.agent.ant.AgentBuildListener.buildFinished (AgentBuildListener.java:85)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.Project.fireBuildFinished (Project.java:1846)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.Main.runBuild (Main.java:688)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.Main.startAnt (Main.java:188)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.launch.Launcher.run (Launcher.java:247)

DEBUG - erver.agent.ant.AntBuildRunner - at org.apache.tools.ant.launch.Launcher.main (Launcher.java:68)

DEBUG - erver.agent.ant.AntBuildRunner - Caused by: java.lang.ClassNotFoundException: java.lang.Enum not found in jetbrains.buildServer.agent.ant.AgentClassLoader{urls=[file:/usr/local/buildAgent/lib/buildServerMessages.jar,file:/usr/local/buildAgent/lib/commons-codec-1.3.jar,file:/usr/local/buildAgent/lib/xpp3_min-1.1.3.4.M.jar,file:/usr/local/buildAgent/lib/buildServerXmlRpcWrapper.jar,file:/usr/local/buildAgent/plugins/antPlugin/lib/buildServerAntServerLogging.jar,file:/usr/local/buildAgent/lib/nanocontainer-1.0-RC-1.jar,file:/usr/local/buildAgent/lib/xmlrpc-2.0.jar,file:/usr/local/buildAgent/lib/buildServerRuntimeUtil.jar,file:/usr/local/buildAgent/plugins/ant/lib/ant-nodeps.jar,file:/usr/local/buildAgent/lib/buildServerCommonRuntime.jar,file:/usr/local/buildAgent/lib/xstream-1.1.2.jar], parent=java.net.URLClassLoader{urls=[file:/usr/local/buildAgent/lib/junit-3.8.1.jar,file:/usr/local/buildAgent/lib/buildServerRuntimeUtil.jar,file:/usr/local/buildAgent/plugins/antPlugin/lib/buildServerAntRunntime.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-vaj.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-weblogic.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-netrexx.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-apache-bsf.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-icontract.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-apache-log4j.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-stylebook.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-xalan1.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-starteam.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-apache-oro.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-junit.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/xercesImpl.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-apache-resolver.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-jsch.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-jmf.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-commons-logging.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-xslp.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/xml-apis.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-apache-bcel.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-swing.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-jai.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-trax.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-commons-net.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-nodeps.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-apache-regexp.jar,file:/usr/local/bui
DEBUG - erver.agent.ant.AntBuildRunner - ldAgent/bin/../plugins/ant/lib/ant-antlr.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-launcher.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-javamail.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/junit.jar,file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-jdepend.jar,file:/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/lib/tools.jar], parent=gnu.gcj.runtime.SystemClassLoader{urls=[file:/usr/local/buildAgent/bin/../plugins/ant/lib/ant-launcher.jar], parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}}}

DEBUG - erver.agent.ant.AntBuildRunner - at java.net.URLClassLoader.findClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.ClassLoader.loadClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at jetbrains.buildServer.agent.ant.AgentClassLoader.loadClass (AgentClassLoader.java:28)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.ClassLoader.loadClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.VMClassLoader.defineClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.ClassLoader.defineClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.security.SecureClassLoader.defineClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.net.URLClassLoader.findClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.ClassLoader.loadClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at jetbrains.buildServer.agent.ant.AgentClassLoader.loadClass (AgentClassLoader.java:28)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.ClassLoader.loadClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - at java.lang.Class.initializeClass (libgcj.so.7)

DEBUG - erver.agent.ant.AntBuildRunner - ...8 more

DEBUG - erver.agent.ant.AntBuildRunner - jetbrains.buildServer.messages.TextMessage

DEBUG - erver.agent.impl.AgentLogProxy - Send buildFinished for 96 OK

0
Comment actions Permalink

Hi Steve,

I guess the problem is in the JDK version. It looks like BuildAgent unable to find
java.lang.Enum class when running the build. Until the next EAP, Build Agents are
capable to run only JDK 1.5 - based builds, and you're probably using 1.4. Is it the case?

Hope this helps,
KIR

0
Comment actions Permalink

That helps some. So here's what's going on:

I'm running this on Fedora Core 5 (which comes with the OSS 1.4 JDK) I have the Sun 1.5 JDK installed and I also have JAVA_HOME environmental variable set to point to the 1.5 JDK directory so TeamServer is running the 1.5 JDK. My build also requires Java 1.5. However, it seems like Ant is still picking up from other files on the system to use Java 1.4 even though JAVA_HOME environmental variable is point to 1.5. I would argue that this should be the responsibility of TeamWare through TeamWare configuration to tell Ant the JDK that it should use. This would make using the product much simpler. This could possibly even be extended to allow configuration of multiple JDKs to use for building. So for example, older verions of our product were targetted at using the 1.4.2 JDK while newer versions use Java 1.5 for building so it could have been helpful to have different branches of the code compiler with different versions of the JDK.

In a related note, the build shows "Success". In this case, the build did not succeed. There is no information shown on the TeamWare web page to show the output of the failure exceptions and show that it did not succeed. I think this needs to be improved.

Thanks,
Steve

0
Comment actions Permalink

That helps some. So here's what's going on:

I'm running this on Fedora Core 5 (which comes with
the OSS 1.4 JDK) I have the Sun 1.5 JDK installed and
I also have JAVA_HOME environmental variable set to
point to the 1.5 JDK directory so TeamServer is
running the 1.5 JDK. My build also requires Java 1.5.
However, it seems like Ant is still picking up from
other files on the system to use Java 1.4 even though
JAVA_HOME environmental variable is point to 1.5.


I guess that in your situation TeamServer just picks java which is available in the
PATH. We'll change it to use JAVA_HOME, if this environment variable is set.
You may watch http://www.jetbrains.net/jira/browse/TW-273 .

I

would argue that this should be the responsibility of
TeamWare through TeamWare configuration to tell Ant
the JDK that it should use. This would make using the
product much simpler. This could possibly even be
extended to allow configuration of multiple JDKs to
use for building. So for example, older verions of
our product were targetted at using the 1.4.2 JDK
while newer versions use Java 1.5 for building so it
could have been helpful to have different branches of
the code compiler with different versions of the
JDK.


Agree here. But even now, it is possible to use different JDK's, but in more complicated way - you have to specify appropriate jdk's in your build script.


In a related note, the build shows "Success". In this
case, the build did not succeed. There is no
information shown on the TeamWare web page to show
the output of the failure exceptions and show that it
did not succeed. I think this needs to be improved.


It's a real bug. Please watch
http://www.jetbrains.net/jira/browse/TW-272

Thanks a lot for your help!
KIR

0
Comment actions Permalink

Along those lines, are you planning on shipping with a JDK, as IDEA does? It does a lot to simplify the out-of-the-box setup/install.

--Dave Griffith

0
Comment actions Permalink

Along those lines, are you planning on shipping with a JDK, as IDEA does? It does a lot to simplify the
out-of-the-box setup/install.

Exactly :).
And if for Jetbrains it's too much work to build with and without JDK/JRE, than maybe this tool from
ex-Jetbrains employees might help(it takes just a few clicks :) ):
http://www.productiveme.com/

and here is how to include the JRE/JDK :) :
http://productiveme.com/blog/?p=7

This tool it's a good example of how easy can be to build, and at least for the moment it's
much more practical than the Teamserver :).

Ahmed.

0
Comment actions Permalink

KIR,

I've added Java 1.5 first in my path and the build now works (well enough for me to debug I think). Thanks for your help! I've added watches to the two items you mentioned. Thanks for your help!

Cheers,
Steve

0
Comment actions Permalink

Ahmed,

Unfortunately, they don't support building of web applications, so this tool is not for us,
at least in their first version.

Kind regards,
KIR

0
Comment actions Permalink

I see no problem here - we can ship with JRE.
The question is, would you really download 80mb instead of 35? ;)

0
Comment actions Permalink

I see no problem here - we can ship with JRE.
The question is, would you really download 80mb instead of 35? ;)

Why "instead"? There should be both possibilities there.

Ahmed.

0
Comment actions Permalink

I think its me who should be thankful here. With your help we've found tough problems
which probably wouldn't be discovered otherwise.

With best regards,
KIR

0
Comment actions Permalink

Unfortunately, they don't support building of web applications, so this tool is not for us,
at least in their first version.

Well, this was meant more ironically :). IMHO many of the features from that tool should
be in fact in TeamServer to be able to use it simply and in a comfortable manner.

Ahmed.

0
Comment actions Permalink

I see no problem here - we can ship with JRE.
The question is, would you really download 80mb

instead of 35? ;)
Why "instead"? There should be both possibilities
there.


And the question is how many people would choose larger distro?
I guess, none from EAP. Or I'm wrong?


Ahmed.

0
Comment actions Permalink

Well, this was meant more ironically :). IMHO many of
the features from that tool should
be in fact in TeamServer to be able to use it simply
and in a comfortable manner.


I think you'll be able to use BuildDesk to create sophisticated build scripts for the TeamServer - they generate Ant scripts.
And you can also use IDEA's embedded facilities to create more simple run configurations (we plan to improve IDEA's build script generation capabilities).
IMO BuildDesk mostly targets not continuous integration builds, but release ones (with all that obfuscation and repackaging).

KIR

0
Comment actions Permalink

>>> I see no problem here - we can ship with JRE.
>>> The question is, would you really download 80mb
>> instead of 35? ;)
>> Why "instead"? There should be both possibilities
>> there.


And the question is how many people would choose larger distro?
I guess, none from EAP. Or I'm wrong?

IMHO you are wrong.
First time users get scared by your long "install steps list".
They need something that can simply downloaded and it just works.

Ahmed.

0
Comment actions Permalink

>> Well, this was meant more ironically :). IMHO many of
>> the features from that tool should
>> be in fact in TeamServer to be able to use it simply
>> and in a comfortable manner.


I think you'll be able to use BuildDesk to create sophisticated build scripts for the TeamServer - they generate Ant scripts.
And you can also use IDEA's embedded facilities to create more simple run configurations (we plan to improve IDEA's build script generation capabilities).
IMO BuildDesk mostly targets not continuous integration builds, but release ones (with all that obfuscation and repackaging).

And I think most of the users won't buy "Yet Another Tool" just to be able to build the product:
The fragmentation is just too high and requires just too many steps.
IMHO users expect from TeamServer to do all those jobs with as less working steps as possible.

Ahmed.

0
Comment actions Permalink

The question is, would you really download 80mb instead of 35?

Heh. Check my e-mail address, and try to imagine the bandwidth I have available.

--Dave Griffith

0
Comment actions Permalink

Would you like to share it for the rest of community :)

Dave Griffith wrote:

The question is, would you really download 80mb instead of 35?

Heh. Check my e-mail address, and try to imagine the bandwidth I have available.

--Dave Griffith

0
Comment actions Permalink

Dave Griffith wrote:

The question is, would you really download 80mb instead of 35?

Heh. Check my e-mail address, and try to imagine the bandwidth I have available.


I don't think my internet connection is particularly bad. I just timed
my download of idea5245.zip and idea5245-dev.zip (together are about
80MB) and it took me 1 minute and 23 seconds. But I am an impatient man
and would prefer to download TeamServer without the jdk if possible.

Bas

0

Please sign in to leave a comment.