moonfire-nvr/docker/build-ui.bash

#!/bin/bash
# This file is part of Moonfire NVR, a security camera network video recorder.
# Copyright (C) 2021 The Moonfire NVR Authors; see AUTHORS and LICENSE.txt.
# SPDX-License-Identifier: GPL-v3.0-or-later WITH GPL-3.0-linking-exception.

# Build the "build-ui" target. See Dockerfile.

set -o errexit
set -o pipefail
set -o xtrace

mkdir /docker-build-debug/build-ui
exec > >(tee -i /docker-build-debug/build-ui/output) 2>&1

date
uname -a
node --version
npm --version
time npm ci
time npm run build

ls -laFR /var/lib/moonfire-nvr/src/ui/node_modules \
    > /docker-build-debug/build-ui/node_modules-after
date
tweak the docker release flows 2021-03-12 15:18:24 -05:00			`#!/bin/bash`
			`# This file is part of Moonfire NVR, a security camera network video recorder.`
			`# Copyright (C) 2021 The Moonfire NVR Authors; see AUTHORS and LICENSE.txt.`
			`# SPDX-License-Identifier: GPL-v3.0-or-later WITH GPL-3.0-linking-exception.`

			`# Build the "build-ui" target. See Dockerfile.`

			`set -o errexit`
			`set -o pipefail`
			`set -o xtrace`

			`mkdir /docker-build-debug/build-ui`
			`exec > >(tee -i /docker-build-debug/build-ui/output) 2>&1`

dockerfile tweaks Most importantly, in build-ui.bash, fix an extra "&&". This meant that if the build command fails, it would proceed and cause confusion. This happened for me: I ran it without the emulation installed. Both the build-server and deploy stages had problems, but because of the "&&" the deploy target didn't actually return failure. After I fixed the emulation problem, there was a bad cached layer. Also save the build output from the dev stage. 2021-03-27 19:34:14 -04:00			`date`
			`uname -a`
clarify support for node 12 and 14 * run node 12, 14, and 16 (next to be supported) on CI. This will catch node version-specific problems like that solved in dad9bdc. * mention 12 and 14 in build instructions and link to instructions for installing that version. * follow this in Dockerfile, installing version 14. This addresses a "Cannot find module 'worker_threads'" error introduced in 39a63e0, which (inadvisedly) upgraded gzipper 4->5 in addition to the material-ui upgrade. * use utf-8 encoding rather than ascii in live part parser. Those builds apparently don't support ascii. iThey must use "small-icu" or have ICU disabled, as described here: https://nodejs.org/api/util.html#util_encodings_supported_when_node_js_is_built_with_the_small_icu_option 2021-08-12 01:27:36 -04:00			`node --version`
			`npm --version`
tweak the docker release flows 2021-03-12 15:18:24 -05:00			`time npm ci`
			`time npm run build`
dockerfile tweaks Most importantly, in build-ui.bash, fix an extra "&&". This meant that if the build command fails, it would proceed and cause confusion. This happened for me: I ran it without the emulation installed. Both the build-server and deploy stages had problems, but because of the "&&" the deploy target didn't actually return failure. After I fixed the emulation problem, there was a bad cached layer. Also save the build output from the dev stage. 2021-03-27 19:34:14 -04:00
tweak the docker release flows 2021-03-12 15:18:24 -05:00			`ls -laFR /var/lib/moonfire-nvr/src/ui/node_modules \`
			`> /docker-build-debug/build-ui/node_modules-after`
dockerfile tweaks Most importantly, in build-ui.bash, fix an extra "&&". This meant that if the build command fails, it would proceed and cause confusion. This happened for me: I ran it without the emulation installed. Both the build-server and deploy stages had problems, but because of the "&&" the deploy target didn't actually return failure. After I fixed the emulation problem, there was a bad cached layer. Also save the build output from the dev stage. 2021-03-27 19:34:14 -04:00			`date`