--
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-mesos+unsubscribe@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/591d4929-47cb-490f-a1bf-bf1f60d98ef4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi there!We've actually produced a binary artifact for libmesos that you can ADD into your Docker image. I believe the intention is to produce these with every version of DC/OS. Right now we have an artifact for DC/OS 1.8.7 which is compatible with Mesos 1.0.2: http://downloads.mesosphere.com/libmesos-bundle/libmesos-bundle-1.8.7-1.0.2.tar.gz.We'll be producing these with each DC/OS release from now on, which should roughly track Mesos versions.You need to set the two environment variables below, replacing $MESOS_SANDBOX with the path to the exploded tarball (the example assumes you are using the Mesos fetcher to pull this tarball down into the sandbox):export LD_LIBRARY_PATH=$MESOS_SANDBOX/libmesos-bundle/libexport MESOS_NATIVE_JAVA_LIBRARY=$MESOS_SANDBOX/libmesos-bundle/lib/libmesos-1.0.1.soHope this helps,Sunil
On Thu, Dec 29, 2016 at 1:52 PM, alexshe via Jenkins Mesos Plugin <jenkin...@googlegroups.com> wrote:
HiMy c++ kung fu is little bit rusty.I need to setup native mesos libs for jenkins.Jenkins runs as docker container.So ive added build procedure to Dockerfile.And it takes forever.Which files should i copy to avoid all this pain with make file?Whole src folder is 2.1 GB.Is there precompiled binaries for mesos native?Why is it so painful? Why not sudo apt-get mesos-dev or something?Thanks
--
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.