b163a52c25
The Zuul unittest jobs were timing out which prompted me to take a look at what might be taking extra time. One thing I noticed is that we're running the yarn build (which runs react-scripts) multiple times when we really only need to run it once. The reason for that is our check to see if zuul web has already built is looking for a file that the builds no longer produce. Update that check to look for a current file and we'll save a bit of time in our jobs and when running things locally. Change-Id: Iae3604fbaf072d53895db850cfc989a832b12b27
83 lines
2.5 KiB
Bash
Executable File
83 lines
2.5 KiB
Bash
Executable File
#!/bin/bash
|
|
# Copyright 2018 Red Hat, Inc.
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
# implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
set -e
|
|
|
|
# This script checks if yarn is installed in the current path. If it is not,
|
|
# it will use nodeenv to install node, npm and yarn.
|
|
# Finally, it will install pip things.
|
|
if [[ ! $(command -v yarn) ]]
|
|
then
|
|
pip install nodeenv
|
|
# Initialize nodeenv and tell it to re-use the currently active virtualenv
|
|
attempts=0
|
|
set +e
|
|
until nodeenv --python-virtualenv -n 16.14.0 ; do
|
|
((attempts++))
|
|
if [[ $attempts > 2 ]]
|
|
then
|
|
echo "Failed creating nodeenv"
|
|
exit 1
|
|
fi
|
|
done
|
|
set -e
|
|
# Use -g because inside of the virtualenv '-g' means 'install into the'
|
|
# virtualenv - as opposed to installing into the local node_modules.
|
|
# Avoid writing a package-lock.json file since we don't use it.
|
|
# Avoid writing yarn into package.json.
|
|
npm install -g --no-package-lock --no-save yarn
|
|
fi
|
|
if [[ ! -f zuul/web/static/index.html ]]
|
|
then
|
|
mkdir -p zuul/web/static
|
|
ln -sfn ../zuul/web/static web/build
|
|
pushd web/
|
|
if [[ -n "${YARN_REGISTRY}" ]]
|
|
then
|
|
echo "Using yarn registry: ${YARN_REGISTRY}"
|
|
sed -i "s#https://registry.yarnpkg.com#${YARN_REGISTRY}#" yarn.lock
|
|
fi
|
|
|
|
# Be forgiving of package retrieval errors
|
|
attempts=0
|
|
set +e
|
|
until yarn install; do
|
|
((attempts++))
|
|
if [[ $attempts > 2 ]]
|
|
then
|
|
echo "Failed installing npm packages"
|
|
exit 1
|
|
fi
|
|
done
|
|
set -e
|
|
|
|
yarn build
|
|
if [[ -n "${YARN_REGISTRY}" ]]
|
|
then
|
|
echo "Resetting yarn registry"
|
|
sed -i "s#${YARN_REGISTRY}#https://registry.yarnpkg.com#" yarn.lock
|
|
fi
|
|
popd
|
|
fi
|
|
pip install $*
|
|
|
|
# Fail-fast if pip detects conflicts
|
|
pip check
|
|
|
|
# Check if we're installing zuul. If so install the managed ansible as well.
|
|
if echo "$*" | grep -vq requirements.txt; then
|
|
zuul-manage-ansible -v
|
|
fi
|