Note that there are some explanatory texts on larger screens.

plurals
  1. POBuilding Android test project with Jenkins fails due to subant error
    text
    copied!<p>When I try to build an Android test project on Jenkins I receive the following error message:</p> <pre><code>BUILD FAILED C:\Progra~1\android-sdk\tools\ant\build.xml:444: The following error occurred while executing this line: C:\Progra~1\android-sdk\tools\ant\build.xml:444: subant task calling its own parent target. </code></pre> <p>This seems somehow to be a known issue (<a href="https://code.google.com/p/android/issues/detail?id=21108">https://code.google.com/p/android/issues/detail?id=21108</a>, <a href="https://wiki.jenkins-ci.org/pages/viewpage.action?pageId=58917193">https://wiki.jenkins-ci.org/pages/viewpage.action?pageId=58917193</a>). As reported, the issue should actually have been fixed, but I am still facing the described problem.</p> <p>I am running Jenkins on a Windows Server, have the latest Android tools installed (SDK tools v22.0.1, platform and build tools v17) and utilizing Ant 1.9.0..</p> <p>The project structure is:</p> <ul> <li>Project A</li> <li>Test Project for Project A</li> </ul> <p>I created a dedicted build job on Jenkins for both of them. The build.xml files for both projects have been created with the "android update" command (as described in the Android specs). So they both are referencing the build.xml from the android-sdk/tools/ant folder. Refering to the Apache Ant specs for subant (<a href="http://ant.apache.org/manual/Tasks/subant.html">http://ant.apache.org/manual/Tasks/subant.html</a>) this might be the source of the failure?!</p> <blockquote> <p>This task must not be used outside of a target if it invokes the same build file it is part of.</p> </blockquote> <p>Has anyone of you encountered similar issues? Any ideas how to solve it?</p> <p>Thanks in advance for your help.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload