I am using Clearcase snapshot views in Hudson and this seems to cause problems with the Ivy project type when it comes to finding build.xml and possibly also ivy.xml (have not come that far though).

An example:

The workspace root for the project is /home/abc/HudsonSlave/workspace/SC_Util_Delta. The snapshot ends up in /home/abc/HudsonSlave/workspace/SC_Util_Delta/hudson_sc_util_delta_view and the build.xml is located in /home/abc/HudsonSlave/workspace/SC_Util_Delta/hudson_sc_util_delta_view/vobs/xyz/scn/sc/util.

I set 'Relative path to descriptor from module root' to vobs/xyz/scn/sc/util/ivy.xml and 'Build File' to vobs/xyz/scn/sc/util/build.xml.

When running the build, the console output says:

Parsing Ivy Descriptor Files
FATAL: Unable to find build script at /home/abc/HudsonSlave/workspace/SC_Util_Delta/hudson_sc_util_delta_view/build.xml

So it seems to ignore the 'Build File' setting as it looks for build.xml in module root. For my non-Ivy projects, I use the same setting and it works fine. I have also tried to prefix the settings with hudson_sc_util_delta_view/ in case the module root is the same as workspace root but this gives the same result. Judging from other command prompts in the console output, the working directory is /home/abc/HudsonSlave/workspace/SC_Util_Delta/hudson_sc_util_delta_view. For non-Ivy projects, the working directory would be /home/abc/HudsonSlave/workspace/SC_Util_Delta/hudson_sc_util_delta_view/vobs/xyz/scn/sc/util.

Am I doing something wrong?

Also, the Ivy plugin seems to require that 'Ant Version' is set to a specific version and not default although that works fine for non-Ivy projects. But that should perhaps be in a separate bug report?