Artifact is deployed to Heroku platform under its full filesystem path in Gradle daemon's directory about heroku-gradle-plugin

[Malax]

Hey @dcmoeller, thanks for the detailed report! I'll investigate and update this issue with my findings.

[Malax]

What was your working directory when you encountered the overly long file paths in scenario three? Can you try again while your working directory is the project directory, if not already the case?

[dcmoeller]

@Malax: All commands shown are issued in project's directory, the one containing build.gradle.

[Malax]

I was able to reproduce this when running with my local Gradle installation (i.e. gradle build deployHeroku). It works correctly when using the Gradle wrapper from the project (./gradlew build deployHeroku). I assume the demon does something that trips off our path resolution code.

Try running the deploy with gradlew as a workaround for now. I'll see that we have a fix for this next week.

[dcmoeller]

Interesting! I've not tried local Gradle installation, I've always used project's Gradle Wrapper ./gradlew ....

[dcmoeller]

I'm using Gradle version 6.5.1. Here it show that both invocations gradle deployHeroku as well as ./gradlew deployHeroku behave the same!

[dcmoeller]

Some more output from my invocations, maybe this helps:

$ ./gradlew deployHeroku
Executed by Gradle 6.5.1

> Task :deployHeroku
-----> Packaging application...
       - app: [APPLICATION]
       - including: /home/[USER]/.gradle/daemon/6.5.1/build/libs/[APPLICATION].jar
-----> Creating build...
       - file: build/heroku/build.tgz
       - size: 13MB
-----> Uploading build...
       - success
-----> Deploying...
remote: 
remote: -----> heroku-gradle app detected
remote: -----> Installing JDK 14... done
remote: -----> Discovering process types
remote:        Procfile declares types -> web
remote: 
remote: -----> Compressing...
remote:        Done: 79.3M
remote: -----> Launching...
[...]

Exactly the same output and outcome if using gradle deployHeroku.

[Malax]

@dcmoeller I started work on a new major version for this plugin which leverages an updated heroku-deploy version that does not show this bug. You can track progress in my draft PR #22. I'm hopeful we can get this out of the door this or at least next week.

[dcmoeller]

Looking forward 😃
By the way, fixed issue myself by modifying one line from my original post containing includes: like this (beware of using absolute path here by using Gradle's buildDir path variable):

includes = ["${buildDir}/libs/[APPLICATION].jar"]

With this you can also modify processTypes(web ...) to the following expected version:

web: "java \$JAVA_OPTS -jar ./build/libs/[APPLICATION].jar" as String

This works.

[Malax]

Hey @dcmoeller, 2.0.0 has been released last friday. Can you confirm it resolves your issue? :)

[dcmoeller]

Confirmed: My "Third szenario" works now 👍
To import new version I have to switch the following clause in build.gradle:

  //classpath 'gradle.plugin.com.heroku.sdk:heroku-gradle:1+'
  classpath 'gradle.plugin.com.heroku.sdk.heroku-gradle:heroku-gradle:2+'

[Malax]

Thanks for confirming and the initial report! 👍