<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 2, 2014, at 6:29 AM, Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu" class="">shijunxiao@email.arizona.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p class="">Dear folks</p><p class="">There are a few instances that build fails on Jenkins due to missing dependency on slaves.<br class="">
All projects that depend on ndn-cxx contains a script in their repository that installs ndn-cxx.<br class="">
Shall we do the same for system package dependencies?</p><p class="">Specifically, a build step of Jenkins script can determine current OS version, and execute either apt-get or MacPorts to install the necessary packages.<br class="">
This would simplify the process of installing new Jenkins slaves</p></div></blockquote><div>Just in case. OS X buildbots do not use macports (it was easier and more uniform to set up using brew).</div><div><br class=""></div><div>We had something like this for several projects (NLSR). The only issue with that I see is OSX 10.8, which requires special way of installing dependencies (which may fail if the process is completely offloaded to project-specific scripts). For all other systems, this can definitely be done.</div><div><br class=""></div><div>—</div><div>Alex</div><div><br class=""></div><br class=""></div><div><br class=""></div><br class=""></body></html>