openstack/project-config
Code Issues Proposed changes

Only publish latest image to magnum

Browse Source 
Currently we were generating images daily, and timestamping it,
also creating the latest one with fedora-atomic-f23-dib name.

This was causing that directory was filled with images daily,
growing in size. There is currently no cleanup process available,
so this cannot be maintained.

So instead of that, we will only publish the latest image, after
validation, with a fixed name. Images are validated and not copied
if they are not successful, so this will be safe to land.

Change-Id: I7fcbb6bed034557969067366e1dc2f51e9fbb1b8
This commit is contained in:
Yolanda Robla 2016-06-02 10:36:55 +02:00
parent 1d0f11c14b
commit 00af7552bb
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
jenkins/jobs/magnum.yaml
View File

@ -80,16 +80,12 @@
./openstack/magnum/magnum/elements/fedora-atomic/install_imagebuild_deps.sh
DATE=`date +%Y%m%d%H%M%S`
IMAGE_NAME="fedora-atomic${DATE}"
IMAGE_NAME="fedora-atomic-f23-dib"
DIB_RELEASE="23" disk-image-create -x -o $WORKSPACE/$IMAGE_NAME fedora-atomic
# validate image
./openstack/magnum/magnum/elements/fedora-atomic/validate_atomic_image.sh $WORKSPACE/${IMAGE_NAME}.qcow2
# copy to latest and upload
cp $WORKSPACE/${IMAGE_NAME}.qcow2 $WORKSPACE/fedora-atomic-f23-dib.qcow2
publishers:
- scp:
site: 'tarballs.openstack.org'