-
Bug
-
Resolution: Not A Defect
-
Minor
-
Jenkins 1.480.2
Gradle 1.0, Gradle 1.4
defaultTasks for a project are not taken into account and not executed.
Output of a commandline call './gradlew tasks':
<snip>
------------------------
All tasks runnable ...
------------------------
Default tasks: check, package
Help tasks
----------
<snip/>
Output of the same project inside jenkins ("Use gradle wrapper"):
<snip>
------------------------
All tasks runnable ...
------------------------
Help tasks
----------
<snip/>
The default tasks are missing, and are therefore not executed.
While working on a workaround, i found the problem: if the project is not checked out into the workspace directly, but into a subfolder (say: trunk), the gradle wrapper ist started, the project is found and run, but gradle gets bent out of shape w/ regard to its internal root project/ project/ module/ folder setup, and does not find default tasks. Weird. Would expect an error message at least.
When checking out into the workspace directly, everything works fine.