/bin/bash /tmp/hudson7923550142805012471.sh Picked up _JAVA_OPTIONS: -Xmx256m
$ /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3/bin/mvn -DTICKET=T-1001 clean Picked up _JAVA_OPTIONS: -Xmx256m [INFO] Scanning for projects...
--
You received this message because you are subscribed to the Google Groups "Jenkins Mesos Plugin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-meso...@googlegroups.com.
To post to this group, send email to jenkin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkins-mesos/6abefd86-050c-47cf-8091-ae236f91c69b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkins-mesos/CALHFn6OwgDJnrZbL2xKEcdMwFjpRCjjWUPqDcR3uSW0JD5Tr3Q%40mail.gmail.com.
Thanks
does it means that for each java process started inside a Mesos slave (maven for example), the content of _JAVA_OPTIONS is taken as parameter?
So if i create a Jenkins slave with 1024MB of RAM, then my maven build will automatically get a -Xmx1024m flag if i don't specify it on the command line?