This message was deleted.

Not sure why it's doing that, but as a workaround you could put them in the

GRADLE_OPT*S*

environment variable

that is true 🙂

I had similar issue with linux tasks before and had to use text block without folding (

|

instead of

>

) plus escaping newlines with

\

at the end of each line. I'm a bit surprised that you run gradle with

run

step instead of

gradle-build-action

though

In Windows Powershell I needed to quote complex

-D

params, something like

-D"org.gradle.java.installations.auto-detect"=false

Not entirely sure if that's this issue you're hitting here, though ;-)

@grossws gradle-build-action version v2.1.0 introduced the ability to configure Gradle with the action without requiring invocations to be managed by the action. This was my first test ...

Ahh, thanks. I'll look into that if it could be useful for my actions

I thought so too... though, if I have to introduce windows-hacks such as

-D"key"=value

or

|

instead of

>

I'm not sure I'd want to move away from just letting the action handle the invocation.