>From build logs: Iotivity-verify-windows-x86-vs2013:
scons VERBOSE=1 TARGET_OS=windows TARGET_ARCH=x86 RELEASE=1 WITH_RA=0 TARGET_TRANSPORT=IP SECURED=1 WITH_TCP=1 BUILD_SAMPLE=ON LOGGING=1 LOG_LEVEL=DEBUG TEST=1 RD_MODE=CLIENT,SERVER ROUTING=EP WITH_UPSTREAM_LIBCOAP=1 MULTIPLE_OWNER=0 -j 4 AUTOMATIC_UPDATE=1 MSVC_VERSION=12.0 iotivity-verify-windows-x86-vs2015: scons VERBOSE=1 TARGET_OS=windows TARGET_ARCH=x86 RELEASE=0 WITH_RA=0 TARGET_TRANSPORT=IP SECURED=0 WITH_TCP=1 BUILD_SAMPLE=ON LOGGING=1 LOG_LEVEL=DEBUG TEST=1 RD_MODE=CLIENT,SERVER ROUTING=EP WITH_UPSTREAM_LIBCOAP=1 MULTIPLE_OWNER=1 -j 4 AUTOMATIC_UPDATE=1 MSVC_VERSION=14.0 Iotivity-verify-windows-amd64-vs2013: scons VERBOSE=1 TARGET_OS=windows TARGET_ARCH=amd64 RELEASE=0 WITH_RA=0 TARGET_TRANSPORT=IP SECURED=0 WITH_TCP=1 BUILD_SAMPLE=ON LOGGING=0 LOG_LEVEL=DEBUG TEST=1 RD_MODE=CLIENT,SERVER ROUTING=EP WITH_UPSTREAM_LIBCOAP=1 MULTIPLE_OWNER=1 -j 4 AUTOMATIC_UPDATE=1 MSVC_VERSION=12.0 Iotivity-verify-windows-amd64-vs2015: scons VERBOSE=1 TARGET_OS=windows TARGET_ARCH=amd64 RELEASE=1 WITH_RA=0 TARGET_TRANSPORT=IP SECURED=1 WITH_TCP=1 BUILD_SAMPLE=ON LOGGING=0 LOG_LEVEL=DEBUG TEST=1 RD_MODE=CLIENT,SERVER ROUTING=EP WITH_UPSTREAM_LIBCOAP=1 MULTIPLE_OWNER=1 -j 4 AUTOMATIC_UPDATE=1 MSVC_VERSION=14.0 -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Mats Wichmann Sent: Friday, May 12, 2017 11:01 AM To: IoTivity Developer List <iotivity-dev at lists.iotivity.org> Subject: [dev] small proposal: document the jenkins build lines seemed like it would be useful to document on the wiki somewhere what the exact build lines are that are used when jenkins verifies a submission. so I grubbed around a bit and came up with this page: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.iotivity.org%2Fjenkins_builders&data=02%7C01%7Cdthaler%40microsoft.com%7Cc1cfa8953c8f493b8a1008d49960e717%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636302088870075492&sdata=Fc5AScMLwsBURfY05pN4g06V7gnGJImZhqLUiMWK9lI%3D&reserved=0 I don't have the Windows incantations, apparently a batch file is built on the fly and run, and I don't know what goes into those (I assume it's not the same as run.bat?). I'm not entirely sure about the arduino and darwin ones either, I guessed that verify-osx calls auto_build with the darwin argument and verify-arduino calls auto_build with the arduino argument, because that's what all the other non-WIndows ones do, but I can't actually see proof of that in Jenkins, at least not where I've looked. The scons calls are generated using the new no-execute mode in auto_build.py (exists in master, not in 1.3-rel, if anyone wanted to reproduce). If someone knows these are not correct, let me know. If they're correct, but this isn't the set we want to be running, let's see if we can make some adjustments. Is this sufficient coverage? -- mats _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev&data=02%7C01%7Cdthaler%40microsoft.com%7Cc1cfa8953c8f493b8a1008d49960e717%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636302088870075492&sdata=UDKVfXIRI0Pxfayrvhk3v4yNfLxVvBQD2Is7fe6ml5Q%3D&reserved=0
