diskimage-builder/diskimage_builder/elements/pip-cache/root.d/01-pip-cache

#!/bin/bash

if [ ${DIB_DEBUG_TRACE:-0} -gt 0 ]; then
    set -x
fi
set -eu
set -o pipefail

PIP_CACHE_DIR=$DIB_IMAGE_CACHE/pip
mkdir -p $PIP_CACHE_DIR

sudo mkdir -p $TMP_MOUNT_PATH/tmp/pip
sudo mount --bind $PIP_CACHE_DIR $TMP_MOUNT_PATH/tmp/pip
Add a pip-cache element. The element bind mounts a pip cache inside the image build chroot so that pip downloads can be reused across image builds. While similar in purpose to the PyPi element that sets up a mirror, this element just allows for a reusable download cache and doesn't require anything to be setup beforehand. The pip-cache element is not concurrency safe, and that is indicated in the README for the element. An upstream bug was file as well: https://github.com/pypa/pip/issues/1141 Change-Id: Ibd1d4ea17c24923ed939357ada95b781e3179cfd 2013-08-14 18:12:15 +00:00			`#!/bin/bash`

Standarise tracing for scripts There is a wide variety of tracing options through the various shell scripts. Some use "set -eux", others explicity set xtrace and others do nothing. There is a "-x" option to bin/disk-image-create but it doesn't flow down to the many scripts it calls. This adds a global integer variable set by disk-image-create DIB_DEBUG_TRACE. All scripts have a stanza added to detect this and turn on tracing. Any other tracing methods are rolled into this. So the standard header is --- if [ "${DIB_DEBUG_TRACE:-0}" -gt 0 ]; then set -x fi set -eu set -o pipefail --- Multiple -x options can be specified to dib-create-image, which increases the value of DIB_DEBUG_TRACE. If script authors feel their script should only trace at higher levels, they should modify the "-gt" value. If they feel it should trace by default, they can modify the default value also. Changes to pachset 16 : scripts which currently trace themselves by default have retained this behaviour with DIB_DEBUG_TRACE defaulting to "1". This was done by running [1] on patch set 15. See the thread beginning at [2] dib-lint is also updated to look for the variable being matched. [1] https://gist.github.com/ianw/71bbda9e6acc74ccd0fd [2] http://lists.openstack.org/pipermail/openstack-dev/2014-November/051575.html Change-Id: I6c5a962260741dcf6f89da9a33b96372a719b7b0 2014-09-04 04:56:29 +00:00			`if [ ${DIB_DEBUG_TRACE:-0} -gt 0 ]; then`
			`set -x`
			`fi`
set -u and -o pipefail everywhere As with the previous similar changes, this is intended to catch problems as they happen instead of ignoring them and continuing on to potentially fail later. Setting this on all existing scripts will allow us to enforce use via Jenkins. Change-Id: Iad2d490c86dceab148ea9ab08f457c49a5d5352e 2014-04-03 02:24:15 +00:00			`set -eu`
			`set -o pipefail`
Add a pip-cache element. The element bind mounts a pip cache inside the image build chroot so that pip downloads can be reused across image builds. While similar in purpose to the PyPi element that sets up a mirror, this element just allows for a reusable download cache and doesn't require anything to be setup beforehand. The pip-cache element is not concurrency safe, and that is indicated in the README for the element. An upstream bug was file as well: https://github.com/pypa/pip/issues/1141 Change-Id: Ibd1d4ea17c24923ed939357ada95b781e3179cfd 2013-08-14 18:12:15 +00:00
Use DIB_IMAGE_CACHE everywhere disk-image-create processes a DIB_IMAGE_CACHE variable and exports it, but there are several elements that ignore the value and wrote out the base location themselves. Use the variable everywhere so that it will get overridden everywhere. Change-Id: I00fff354d6c931ad67cf3052d055f0e4604dfdc8 2014-10-05 20:55:34 +00:00			`PIP_CACHE_DIR=$DIB_IMAGE_CACHE/pip`
Add a pip-cache element. The element bind mounts a pip cache inside the image build chroot so that pip downloads can be reused across image builds. While similar in purpose to the PyPi element that sets up a mirror, this element just allows for a reusable download cache and doesn't require anything to be setup beforehand. The pip-cache element is not concurrency safe, and that is indicated in the README for the element. An upstream bug was file as well: https://github.com/pypa/pip/issues/1141 Change-Id: Ibd1d4ea17c24923ed939357ada95b781e3179cfd 2013-08-14 18:12:15 +00:00			`mkdir -p $PIP_CACHE_DIR`

			`sudo mkdir -p $TMP_MOUNT_PATH/tmp/pip`
			`sudo mount --bind $PIP_CACHE_DIR $TMP_MOUNT_PATH/tmp/pip`