It appears that any time you execute Gradle and it doesn’t find a build file, it still exits with a 0 return code. This causes issues in our CI environment where the build is reported as a success when it never happened.
The ultimate issue is that the CI config is looking in the wrong place for the build file. However, it results in confusing output when Gradle doesn’t actually fail because of this.
Is there a reason for the behavior, or has no one brought this up before?
:help Welcome to Gradle 1.0-milestone-4. To run a build, run gradle <task> ... To see a list of available tasks, run gradle tasks To see a list of command-line options, run gradle --help BUILD SUCCESSFUL