On 04/21/2017 02:26 AM, Way Vadhanasin via iotivity-dev wrote: > 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
I asked this question in some form a while back, and came away with the impression that TEST=1, needed for the unittests, required SECURED=0. I may have misunderstood that reply. We do need to make sure that testing happens in a context that is as close as possible to what will go into production, so I agree this needs to be examined and at least one qualifying test run needs to be with SECURED=1.
