Hi Trevor, The previous request is valid when removing some build jobs can shorten the build verification waiting time.
Anyway, the following build job needs to be added at least. https://build.iotivity.org/ci/job/iotivity-verify-linux_unsecured_with_tcp/44/ This build was only valid on rel-1.1 branch work now. BR, Uze Choi -----Original Message----- From: ???(Uze Choi) [mailto:[email protected]] Sent: Thursday, September 01, 2016 11:34 AM To: 'Trevor Bramwell' Cc: 'iotivity-helpdesk at rt.linuxfoundation.org'; 'iotivity-dev at lists.iotivity.org' Subject: RE: Question for build machines capability and queue handling of Jenkins Hi Trevor, If there is no concern/objection until today for following job removal, let's remove them. https://build.iotivity.org/ci/job/iotivity-verify-linux_unsecured/2023/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-linux_secured_with_ra/2015/ : SUCCESS -> let's remove it https://build.iotivity.org/ci/job/iotivity-verify-arduino/2027/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-simulator/2037/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-linux_secured_with_rd/2009/ : SUCCESS -> let's remove it https://build.iotivity.org/ci/job/iotivity-verify-linux_secured/2034/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_x86/2036/ : SUCCESS -> let's remove it https://build.iotivity.org/ci/job/iotivity-verify-linux_unsecured_with_rd/2037/ : SUCCESS -> let's remove it https://build.iotivity.org/ci/job/iotivity-verify-unit_tests/2013/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-windows-vs2015/2216/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-osx/2401/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi/2034/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-windows-vs2013/327/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-linux_unsecured_with_ra/2024/ : SUCCESS -> let's remove it https://build.iotivity.org/ci/job/iotivity-verify-tizen/2034/ : SUCCESS Do we need to check the Windows build for both tool from vs2015/2013 together? BR, Uze Choi -----Original Message----- From: Trevor Bramwell [mailto:[email protected]] Sent: Thursday, September 01, 2016 8:36 AM To: ? (Uze Choi) Cc: iotivity-helpdesk at rt.linuxfoundation.org; iotivity-dev at lists.iotivity.org Subject: Re: Question for build machines capability and queue handling of Jenkins Hi Uze and Developers, On Wed, Aug 31, 2016 at 03:45:01PM +0900, ? (Uze Choi) wrote: > Hi Trevor, > We have a hard time to get the verified state from Jenkins machine. > Some commits takes one day as below. From the next week, I expect it > will take longer due to more fixes from QA result. > This looks very critical problem in IoTivity release. Our queue is continuing to be backed up due to low bandwidth between Jenkins build servers and the datacenter hosting Gerrit, and adding more resources may only make the problem worse. I've been informed that this issue should be resolved on Saturday once a router in the datacenter hosting Gerrit is rebooted. This was decided as the best time since this router services multiple projects and other services. Until then I'm doing what I can to reduce traffic between Jenkins and Gerrit, as cloning the repo currently still takes 4-6 minutes. > And, I watched some strange behavior from upper cases. > Later commit result in earlier verification result from earlier commit. > > Please guide us what to do for performance improvement. This is most likely due to me disabling 'Build newest patchset only', when trying to diagnose timeout issues. I've re-enabled it. There easiest way to help imporove performance is by not publishing multiple patchsets a minute, and testing changes locally before pushing. I've seen too many changesets with 30-40 patches, each one either requiring verification or causing churn in the build system as Jenkins has to first abandon the previous change. I have also put up two patches for review to help the build system: 1) Splitting Android builds into 3 parts: https://gerrit.iotivity.org/gerrit/#/c/10239/ This should reduce the turn around time in patches 2) Removing false positives: https://gerrit.iotivity.org/gerrit/#/c/11087/ auto_build.py is not exposing error codes, causing some builds which should fail to pass. Regards, Trevor Bramwell
