The build should be exactly the same as if you're running it from the command
line of another machine.
I tell the developers that builds should be simple: I define a small needed set
of tools, Subversion, JDK 1.6, and Ant 1.8. I should be able to checkout and
build by just typing "ant".
If you can do that, you should be nothing else except hitting the correct ant
target in your build.xml.
Of you need to put the jars in a specific directory and set some sort of
variable on your machine in order to do a build, you have to do the same on
Jenkins.
--
David Weintraub
da...@weintraub.name
On Aug 27, 2012, at 12:58 PM, praneeth <praneeth.ku...@rediffmail.com> wrote:
> Hi,
>
> Many thanks for your reply...I will try removing the build file filed
> empty..one more question is it necessary to specify the jar file path when
> running through jenkins???
> <property name="ws.home" value="${basedir}"/>
> <property name="ws.jars" value="C:\selenium server"/>
> <property name="test.dest" value="${ws.home}/build"/>
> <property name="test.src" value="${ws.home}/src"/>
> <property name="ng.result" value="test-output"/>
>
> Regards
> praneeth
>
> On Monday, 27 August 2012 12:37:34 UTC+1, praneeth wrote:
> Hi
>
> Can you please let me know how can i set ant as a global environment variable
> in jenkins configuration..?
>
> Regards
> praneeth
