Hudson build doesn't work when run in browser, but works from command line
I am creating a new Hudson task (in WinXP) for a project that generates javascript files and does xslt transformations as part of the build process.
The ant construct does not work for XSL transformations when run from Hudson, but it works fine when the same assembly on the same database (that is, in the Hudson workspace) is run from the command line.
Error message:
line 208: the variable "screen" is propagated in the same area.
I tried to configure Hudson to use both ant directly and to use the script package - both were abandoned in Hudson.
I tried in Firefox, IE6 and Chrome and saw the same problem.
Can anyone suggest how we can fix this with Hudson?
a source to share
The problem has been resolved.
Our build actually depends on jdk 1.4.2 and Hudson seems to work using 1.6. When I started Hudson to run as a service, it was running as my local user, which meant that it took the 1.4.2 JAVA_HOME environment variable and therefore worked.
I think another possible solution is to configure Hudson to use 1.4.2 by default.
a source to share
I would assume this is not a problem with Hudson directly, as it is with the script construct and / or the environment itself.
Is your build script relying on certain environment variables defined or worse, work done from a specific directory structure (i.e. it works if it is done from under / home / mash / blah but not from another directory e.g. / tmp)? Is the assembly script a reference to external files with relative paths?
This is what I would like to explore. For environment variables, you can tell Hudson to pass them to Ant. For other questions, you probably want to change your build script. Check the console output provided by Hudson and perhaps install Ant to print verbose / debug messages to get a better understanding of the environment / files.
a source to share