gradlew could not be started

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

gradlew could not be started

Joan
Trying to run the gradle wrapper through the artifactory gradle plugin is not working, and it’s not clear why not. When using the default ‘./gradlew’, the error was FileNotFound. When using ${bamboo.build.working.directory}/gradlew as the path, the error is gradlew could not be startedcom.atlassian.utils.process.ProcessNotStartedException, with no clues as to why the process doesn’t start. This is on redhat linux. On logging in to the machine, to the directory in question, starting gradlew manually works just fine. Web search hasn’t helped. Trying to get clues using a Bash task, running ${bamboo.build.working.directory}/gradlew also started okay. So what is going on?

Thank you for any help.

—Joan

------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

Re: gradlew could not be started

Joan
Just to follow up: this turned out to be due to a bug in how bamboo copies shared source control folders - it was turning off the executable bit for gradlew. A script task to turn it back on solved the problem.