On Fri, Aug 7, 2015 at 6:37 AM, Rafael Ribeiro Rezende <[email protected]> wrote: > if I understood well, the only way to force this Ant installation to use > another JAVA_HOME is by resetting the env variable in console before > starting my Jenkins instance. Is that right?
You could · set $JAVA_HOME as a variable accessible to the whole `Run`, for example by using node properties · fix JENKINS-29144 and use a version of Jenkins core with the fix · implement `Step` from `workflow-step-api` directly (rather than implementing `SimpleBuildStep` to share the class with the freestyle publisher) and get the contextual `EnvVars` The third option seems most practical, though it is somewhat more intrusive. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1DgNfotcCA1VScCC3ioB03BZ7xKiX_t-S3AgHkOt%2B6Cw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
