Hi Trevor, There are lots of meaningless Android build checks. I pushed the code to resolve this issue on master/1.2-rel branch together. https://gerrit.iotivity.org/gerrit/#/c/12023/
Could you trigger only build_android removing below 12 android builds. (./auto_build.sh android) I create the build_linux_secured_with_tcp, please add this build job (./auto_build.sh linux_secured_with_tcp) BR, Uze Choi -----Original Message----- From: Trevor Bramwell via RT [mailto:iotivity-helpd...@rt.linuxfoundation.org] Sent: Wednesday, September 21, 2016 6:06 AM To: uzchoi at samsung.com Cc: iotivity-dev at lists.iotivity.org Subject: [IoTivity Helpdesk #30250] FW: SECURE build flag setting as default configuration Hi Uze, Responding to your comments on Android as 'SECURED' is already being addressed on the mailing list. On Mon Sep 19 06:35:26 2016, uzchoi at samsung.com wrote: > Hi Trevor, > Sooner, I?ll request this change into Jenkins Job setting. > Additionally, let me explain the android build fragmentation. All like > not so useful for various options. > What is the rm option? rm adds '-DROUTING_GATEWAY=1' to the build. > we need to pick up single profile from each architecture below. > https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi- > ble/5/ : SUCCESS > https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi- > bt/5/ : SUCCESS > https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi- > ip/5/ : SUCCESS > https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi- > rm_and_ble/5/ : SUCCESS > https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi- > rm_and_bt/5/ : SUCCESS > https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi- > rm_and_ip/5/ : SUCCESS > https://build.iotivity.org/ci/job/iotivity-verify-android_x86-ble/5/ : > SUCCESS > https://build.iotivity.org/ci/job/iotivity-verify-android_x86-bt/5/ : > SUCCESS > https://build.iotivity.org/ci/job/iotivity-verify-android_x86-ip/5/ : > SUCCESS > https://build.iotivity.org/ci/job/iotivity-verify-android_x86- > rm_and_ble/5/ : SUCCESS > https://build.iotivity.org/ci/job/iotivity-verify-android_x86- > rm_and_bt/5/ : SUCCESS > https://build.iotivity.org/ci/job/iotivity-verify-android_x86- > rm_and_ip/5/ : SUCCESS > BR, Uze Choi All of are the builds originally being ran by './auto_build.sh android_x86' and './auto_build.sh android_armeabi'. I merely split them up individually so that instead of running two 1-1.5 hour builds, we could run six ~15-20 minute builds. This allows the android verification to take advantage of build servers that may become free while verification is happening.
