Hi all, Recently CJ has updated some of the static extlibs used in Jenkins to be git repos, so that it's possible to have scons switch them to correct tags/branches. My initial change<https://gerrit.iotivity.org/gerrit/#/c/17181/> to make that happen for libcoap has sparked a discussion, if we want to rely on a network connection during builds or not.
Currently identified pros: * No need to contact CJ every time there's a change in extlibs, so he can update Jenkins. We would only need to change the scons script. * The whole process would be automated even for the developers' local builds. Currently identified cons: * We make the developer implicitly rely on network connectivity without his/her knowledge. That might be unwanted in case you're currently working with limited/metered internet connection. The current approach employed by the extlibs maintainers is to not rely on the internet connection, but there is no well-defined policy we should stick to. Personally, I think there might be a way to combine the best of the two worlds: * Make Jenkins builds attempt automatic extlibs updates, if they are not on the correct commit already. * Have the developers' builds behave the same way they do right now. This could be achieved by making scons check an additional environment variable or a scons argument, which could be set explicitly for Jenkins builds. Since every build right now will fail anyway, if you're not using the correct version of an extlib (scons will just print instruction how to get it), I think this might be a reasonable solution. What are your opinions? Thanks, Pawel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170213/782fcd25/attachment.html>
