5df024e716
This approach was used instead of fetching the latest version number at build time because that meant a CoreOS update could break our gates at any given time. A new CoreOS make target, 'pin_latest', was made available. This target bumps the "pinned" version to the latest. An eventual proposal bot will call this target to ensure we stay up to date. This also offers the possibility for downstream operators that want to build the latest version to call this target before building. This leads to the same result as fetching directly in the python build script, but with more flexibility. This is a second attempt to merge this change, as before it caused frequent CI failures/timeouts. The expectation is that with CoreOS only gating on IPA, this would be lower impact and easier to mitigate. Change-Id: I78cb2efff2293b1591b30b7e39df9fc2af98d0b2 Closes-bug: 1581673 Co-Authored-By: Arun S A G <sagarun@gmail.com> Co-Authored-By: Jim Rollenhagen <jim@jimrollenhagen.com>
29 lines
547 B
Makefile
29 lines
547 B
Makefile
BUILD_DIR=UPLOAD
|
|
KERNEL=$(BUILD_DIR)/coreos_production_pxe.vmlinuz
|
|
INITRD=$(BUILD_DIR)/coreos_production_pxe_image-oem.cpio.gz
|
|
|
|
default: docker coreos
|
|
|
|
docker:
|
|
./docker_build.bash
|
|
|
|
coreos:
|
|
mkdir -p $(BUILD_DIR)
|
|
./coreos-oem-inject.py oem $(BUILD_DIR)
|
|
|
|
clean:
|
|
rm -rf ironic-python-agent
|
|
rm -f oem/container.tar.gz
|
|
rm -f $(INITRD)
|
|
rm -f $(KERNEL)
|
|
rm -rf ../.image_cache
|
|
|
|
docker_clean:
|
|
./docker_clean.bash
|
|
|
|
iso: docker coreos
|
|
./iso-image-create -o $(BUILD_DIR)/ipa-coreos.iso -i $(INITRD) -k $(KERNEL)
|
|
|
|
pin_latest:
|
|
./pin_latest_coreos.sh
|