Jenkins reports The SDK directory 'H:\Android\android-sdk' does not exist

[Mark Elston]

I am using Jenkins to build several related projects including an Android APK project.  If I execute the gradlew.bat file from within the android project directory on the build machine (on the command line) then everything builds just fine.  However, when using the Gradle Wrapper from Jenkins I get the error in the subject.

The H: drive is not where Jenkins is executing.  I don't know if that is the problem or not.  Unfortunately, the build machine has very limited space on the C drive so I can't put the Android SDK on it (6G is just too much).  So I installed it on H:.  As I said, Gradle finds it just fine when run from the command-line.

What is causing Jenkins to report that a directory that *does* exist doesn't exist?

Mark

[Eric Pyle]

Assuming that H: is a network drive, if Jenkins is running as a service under the default Local System account, it will not have access to network resources. Jenkins needs to run as a user with network privileges.

Eric

--
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 jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/67920d6b-c5c8-4cca-b789-0fdf476965bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mark Elston]

Thanks for helping out with that.  I now need to figure out how to change the Jenkins service.

Mark

[Mark Elston]

OK.  Looking at the services on the build machine Jenkins is running logged on as me.  So I am not sure why it can't see the network drive.

Mark

[Mark Elston]

Ah, it turns out that services, even though they 'log in' under a user account, don't go through all the normal login process so network drives are not mapped.  I need to make other arrangements.

Mark