Feature request - env options

[ZacSweers]

We set some env options dynamically on our builds due to github not preserving them between steps, and in our case they're computed. It would be great if there was an option like run_init that accepted something arbitrary to run before the gradle command

[eskatos]

Hi @ZacSweers,
Is that a common practice? Could you please share some pointers showing how this would be done from a workflow point of view?

[ZacSweers]

I don't have a public example but there re some cases where we run commands with local env vars

FOO=bar ./gradlew build

[ZacSweers]

A better example would be env vars that gradle or other plugins (like the android plugin seek)
https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_environment_variables

We may dynamically set the JDK in a conditional way that can't be statically defined in github actions' env argument alone, hence wanting a script to manage it.

[eskatos]

Hi Zac,

I can see how this could be useful. Thanks for clarifying.
I don't have that immediate need so it may take a while before I implement that myself.
Happy to review a pull request though ;)

It is somewhat related to #18 and should be made consistent form the YAML point of view.

[bigdaz]

With gradle-build-action@v2.1 it is now possible to use the action to configure Gradle and use a standard run action for the actual Gradle invocation. This should allow you to benefit from the caching this action provides, but retain your existing step that invokes Gradle, including any scripted setup of the environment.