User Tools

Site Tools


how_to_make_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
Next revision
Previous revision
how_to_make_build_changes [2017/09/19 19:42]
Mats Wichmann
how_to_make_build_changes [2018/07/19 23:20] (current)
Trevor Bramwell
Line 3: Line 3:
 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 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 ​CJ Collier from Linux Foundation. I have found the best way to start a work item is to draft an email (which is then converted to a ticket on LF’s side) and send it to '​iotivity-helpdesk@rt.linuxfoundation.org'. CJ is usually the person to pick these items up. If there is more prep work on your side to do, he is pretty good at letting you know what is able to do and what you should do before ​he can actually take action+To gain access to the above Jenkins page and/or to gain more insight into how the build machine is actually configured, please contact ​[[mailto:helpdesk@iotivity.org|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.
- +
-In addition to CJ, you may contact me (Joey Morrow <​joseph.l.morrow@intel.com>​) and I will either help you or point in the direction you can find more help.+
  
 Also note there are some suggestions for changes to building at [[build_changes]],​ feel free to add items for discussion there. 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 [[https://​git.iotivity.org/​ci-management/​tree/​packer/​provision/​roles/​iotivity/​vars/​packages.yaml|packages.yaml]] and submit the change to Gerrit.
 +
 +Once the change is reviewed and merged, a packer [[https://​jenkins.iotivity.org/​view/​ci-management/​job/​ci-management-packer-merge-ubuntu-16.04-builder/​|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 [[mailto:​helpdesk@iotivity.org|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 [[https://​lists.iotivity.org|iotivity-dev]] mailling list stating the image has been verified and put into production
how_to_make_build_changes.1505850142.txt.gz · Last modified: 2017/09/19 19:42 by Mats Wichmann