CF ungracious failure on CF-PUSH when Target Resources Exhausted

[jnorthr]

While testing version 1.0.2 of the CF gradle plugin, my anynines.com target only allows a maximum of resources. i did not see that i had exceeded their limit and tried a CF-PUSH to that target. The gradle plugin failed with http response code 400 because of it and forced a java dump in my joblog thus killing my gradle script. Do we have a way to programatically see the exit code for the CF plugin after the completion of a CF task ?

can send you a full trace log by email if you need it but here is the relevant extracts:

18:12:04.031 [DEBUG] [org.gradle.api.Task] REQUEST: POST https://api.de.a9s.eu/v2/apps
18:12:04.031 [DEBUG] [org.gradle.api.Task] RESPONSE: 400 ERROR 400 Bad Request
18:12:04.046 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter] Finished executing task ':asciidoctor-project:cf-push'

18:12:04.718 [ERROR] [org.gradle.BuildExceptionReporter] Caused by: org.cloudfoundry.client.lib.CloudFoundryException: 400 Bad Request (You have exceeded your organization's memory
limit. Please login to your account and upgrade. If you are trying to scale down and you are receiving this error, you can either delete an app or contact support.)
18:12:04.734 [ERROR] [org.gradle.BuildExceptionReporter] at org.cloudfoundry.client.lib.rest.CloudControllerResponseErrorHandler.getException(CloudControllerResponseErrorHand
ler.java:69)

[scottfrederick]

Gradle tasks throw exceptions when something goes wrong, and these exceptions fail the build. This is the typical behavior of plugins, not just the CF plugin. There might be a way to catch the specific CloudFoundryException being throw in this case and react to it in the build script, but I don't know of the top off my head how this would be done in Gradle.

If you simply need the build to continue even after a failure like this, you can pass the --continue option on the Gradle command line. Is there some other action you would want the build script to take in this case?

[jnorthr]

no, thats quite a good idea !
--continue scott ;-}
thx

On 11 February 2014 21:10, Scott Frederick notifications@github.com wrote:

Gradle tasks throw exceptions when something goes wrong, and these
exceptions fail the build. This is the typical behavior of plugins, not
just the CF plugin. There might be a way to catch the specific
CloudFoundryException being throw in this case and react to it in the
build script, but I don't know of the top off my head how this would be
done in Gradle.

If you simply need the build to continue even after a failure like this,
you can pass the --continue option on the Gradle command line. Is there
some other action you would want the build script to take in this case?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/137#issuecomment-34800138
.