User Tools

Site Tools


how_to_make_build_changes

The build script is found at the root of the IoTivity repository. Please see auto_build.sh in master branch; the work is actually done by auto_build.py

To see how Jenkins calls this script (and to see partial build system configuration) see this publicly viewable page: https://build.iotivity.org/ci/view/iotivity/job/iotivity-verify-unit_tests/configure

To gain access to the above Jenkins page and/or to gain more insight into how the build machine is actually configured, please contact IoTivity Helpdesk at The Linux Foundation. If there is more prep work on your side to do, they is pretty good at letting you know what is able to do and what you should do before they can actually take action.

Also note there are some suggestions for changes to building at build_changes, feel free to add items for discussion there.

Adding Packages to the Build Servers

Packages installed on the build servers are listed in an Ansible var file, which is used during a Packer build. To include a new package on the Ubuntu build servers, modify packages.yaml and submit the change to Gerrit.

Once the change is reviewed and merged, a packer build will start. Once the build completes, the line in the build log like:

Creating the image: ZZCI - Ubuntu 16.04 - builder - 20180719-175641.320

Will need to be forwarded to helpdesk and requested that the new image be put in production.

An email from someone on The Linux Foundation Releng team should then be seen on the iotivity-dev mailling list stating the image has been verified and put into production

how_to_make_build_changes.txt · Last modified: 2018/07/19 23:20 by Trevor Bramwell