Jenkins appears to be building and running tests in services with SECURED=0. When I tried to build these tests with SECURED=1, a big portion of them failed. Is it time to remove SECURED=0 configuration out of Jenkins gate or am I missing something? At the very least, we need to mandate that the location of code that gets tested with SECURED=0 should also be tested with SECURED=1 (I filed IOT-2096<https://jira.iotivity.org/browse/IOT-2096>).
Thoughts? Thanks, Way -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170421/a9d5d52b/attachment.html>
