I just upgraded from Jenkins 1.501 to 1.513 and from that on, no Rake task was 
working any more.

We have only one Ruby/Rake version installed so we used in all projects the 
"(Default)" configuration.

So for testing purpose I configured a small test job that only should trigger a 
single Rake task. From the console I get this strange output:

        [EnvInject] - Loading node environment variables.
        Building on master in workspace G:\Hg\JenkinsCI\jobs\00Test\workspace
        [workspace] $ rake.bat default
        ruby.exe: No such file or directory -- 
G:/Hg/JenkinsCI/jobs/00Test/workspace/rake (LoadError)
        Build step 'Invoke Rake' marked build as failure
        Finished: FAILURE

When I change inside Job configuration the name of the used Ruby installation 
from ("Default") to the configured name - in my case it was default -, then 
Jenkins complains that no cygwin is installed???

Then I reverted my Jenkins configuration back version 1.501 (fortunately we 
have the complete Jenkins under version control) and I get the same error!?? 
Rather strange! That configuration worked for us for several month.

Then I looked further what has changed that day and via the Windows patches, 
Java was updated to 7.0.21.
Then I de-installed this version and re-installed version 7.0.17 and suddenly 
Jenkins 1.501 and 1.513 work as expected.

Then I get this console output:

        [EnvInject] - Loading node environment variables.
        Building on master in workspace G:\Hg\JenkinsCI\jobs\00Test\workspace
        [workspace] $ rake.bat default
        I was here
        Finished: SUCCESS


I am pretty sure that I cannot convince our IT department to stay for a longer 
time on an old Java version |-)

Is this a known issue? Is there a known workaround?

Many thanks in advance and regards, 
Felix

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to