User Tools

Site Tools


build_changes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
build_changes [2017/10/31 19:19]
Mats Wichmann
build_changes [2018/05/29 15:34] (current)
Mats Wichmann
Line 4: Line 4:
 Proposals for build system improvements,​ please comment on individual idea on mailing list, or add suggestions here. Proposals for build system improvements,​ please comment on individual idea on mailing list, or add suggestions here.
  
-  * Get Jenkins builders off of Ubuntu 12.04. 12.04LTS is now out of support and has us pegged to some very old versions of needed packages (like scons, and the coverage report generator gcovr). It also gives us some false success - there is at least one unit test (stack/​tests/​stacktests) that happens to pass on this old version, but all more recent Linux systems time out the test (deadman timer exception)+  ​* **DONE** Get Jenkins builders off of Ubuntu 12.04. 12.04LTS is now out of support and has us pegged to some very old versions of needed packages (like scons, and the coverage report generator gcovr). It also gives us some false success - there is at least one unit test (stack/​tests/​stacktests) that happens to pass on this old version, but all more recent Linux systems time out the test (deadman timer exception)
   * Use a consistent scons version (see also previous item). This is mostly for Linux: other platforms don't have a "​distro version"​ of scons but rather install it via pip during provisioning. Note the recent release of 3.0 higlighted that the problem is not only distro-version too old, it can also be upstream (pip) version is too new. For linux, install it directly, perhaps in a virtualenv, and don't use distro version? ​ [[https://​jira.iotivity.org/​browse/​IOT-2755|IOT-2755]].   * Use a consistent scons version (see also previous item). This is mostly for Linux: other platforms don't have a "​distro version"​ of scons but rather install it via pip during provisioning. Note the recent release of 3.0 higlighted that the problem is not only distro-version too old, it can also be upstream (pip) version is too new. For linux, install it directly, perhaps in a virtualenv, and don't use distro version? ​ [[https://​jira.iotivity.org/​browse/​IOT-2755|IOT-2755]].
-  * Install the Gerrit trivial-rebase functionality. This would let patchsets which don't change code (e.g. rebase, comment change) collect and retain votes and comments made against the previous version.+  ​* **DONE** Install the Gerrit trivial-rebase functionality. This would let patchsets which don't change code (e.g. rebase, comment change) collect and retain votes and comments made against the previous version.
   * Update out of date build tools appropriately. ​ In particular, the Android SDK and NDK are quite out of date, but an uplift has a number of moving parts - in the code tree it needs to be tested carefully before the builder can be adjusted. ​   * Update out of date build tools appropriately. ​ In particular, the Android SDK and NDK are quite out of date, but an uplift has a number of moving parts - in the code tree it needs to be tested carefully before the builder can be adjusted. ​
   * Unit-test data collection:   * Unit-test data collection:
build_changes.1509477559.txt.gz ยท Last modified: 2017/10/31 19:19 by Mats Wichmann