Commit ada1d7b8 authored by Lorenzo Martinico's avatar Lorenzo Martinico

Add an option to enable dev_server for the build

parent 88bf234f
...@@ -40,6 +40,7 @@ In the vifib parameters (softinst\<nb\>.host.vifib.net \> Services \> Parameters ...@@ -40,6 +40,7 @@ In the vifib parameters (softinst\<nb\>.host.vifib.net \> Services \> Parameters
* **board** / ex: peppy, swanky, ... Complete list of devices and board names on [chromiumOS developer guide](http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices) * **board** / ex: peppy, swanky, ... Complete list of devices and board names on [chromiumOS developer guide](http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices)
* **branch** / ex: release-R46-7390.B (you can find the release in the [Chromium OS source tree](https://chromium.googlesource.com/chromiumos/manifest/+refs)) * **branch** / ex: release-R46-7390.B (you can find the release in the [Chromium OS source tree](https://chromium.googlesource.com/chromiumos/manifest/+refs))
* **keep_cache** / yes|no (choosing "no" saves about 15Go of disk space per board, choosing "yes" will makes next build faster and less expensive in term of needed ressources because of not rebuilding everything) * **keep_cache** / yes|no (choosing "no" saves about 15Go of disk space per board, choosing "yes" will makes next build faster and less expensive in term of needed ressources because of not rebuilding everything)
* **dev_server** / yes|no Enables devserver to configure over the air updates and install packages after build. Probably should not be used in production
//Choosing board daisy will accept all licenses for the daisy board build only, in order to use Mali drivers, see [chromium mailing list](https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-dev/Pf9ZG2itxWM) //Choosing board daisy will accept all licenses for the daisy board build only, in order to use Mali drivers, see [chromium mailing list](https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-dev/Pf9ZG2itxWM)
......
...@@ -109,6 +109,7 @@ context = ...@@ -109,6 +109,7 @@ context =
key branch parameters:configuration.branch key branch parameters:configuration.branch
key boards_list parameters:configuration.boards key boards_list parameters:configuration.boards
key keep_cache parameters:configuration.keep_cache key keep_cache parameters:configuration.keep_cache
key dev_server parameters:configuration.dev_server
key ebuilds_dir nayuos-ebuilds:location key ebuilds_dir nayuos-ebuilds:location
raw scripts_dir {{ software_dir }}/scripts raw scripts_dir {{ software_dir }}/scripts
raw logo_dir {{ software_dir }}/logo raw logo_dir {{ software_dir }}/logo
......
...@@ -329,7 +329,13 @@ for board in ${BOARDS} ; do ...@@ -329,7 +329,13 @@ for board in ${BOARDS} ; do
# NayuOS images # NayuOS images
date >> "${BUILD_LOG}" date >> "${BUILD_LOG}"
echo "building image" >> "${BUILD_LOG}" echo "building image" >> "${BUILD_LOG}"
cros_sdk --nouse-image -- ./build_image --board=${board} dev >> "${BUILD_LOG}" \ if [ {{ dev_server}} == "yes" ] ; then
cros_sdk -- ./start_devserver &
ROOTFS_VERIFICATION_FLAG = "--noenable_rootfs_verification"
else
ROOTFS_VERIFICATION_FLAG = ""
fi
cros_sdk --nouse-image -- ./build_image $ROOTFS_VERIFICATION_FLAG --board=${board} dev >> "${BUILD_LOG}" \
&& cros_sdk -- rm -f $NAYU_IMAGE_LOCATION && cros_sdk -- touch $NAYU_IMAGE_LOCATION \ && cros_sdk -- rm -f $NAYU_IMAGE_LOCATION && cros_sdk -- touch $NAYU_IMAGE_LOCATION \
&& cros_sdk -- cros flash --board=${board} file://$NAYU_IMAGE_LOCATION >> "${BUILD_LOG}" \ && cros_sdk -- cros flash --board=${board} file://$NAYU_IMAGE_LOCATION >> "${BUILD_LOG}" \
&& cros_sdk -- ./test_nayuos_image ${board} > "${TEST_LOG}" \ && cros_sdk -- ./test_nayuos_image ${board} > "${TEST_LOG}" \
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment