cr-daily-branch: libvirt: use frozen version on stable branches

libvirt master might increase its LIBXL_API_VERSION.  When this feeds
through osstest it can cause the push gates of Xen stable branches to
break.

So for stable Xen branches do not track libvirt upstream.  Instead,
use a frozen revision.  (Only for main push gate tests of stable Xen
branches.)

The frozen branch is never going to be updated so it is not suitable
for other kinds of uses.  In particular it won't get security fixes.
So we call the refs   osstest/frozen/xen-K.L-testing  to discourage
users from using them.

Deployment note: The Xen release checklist needs a new item "add this
frozen libvirt branch".

Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>

diff --git a/cr-daily-branch b/cr-daily-branch
index 8b7c789c5643c531c9b743863c66a24a6fef7565..21780b8b32a96600f1663a21e2a575941d782c8a 100755 (executable)
--- a/cr-daily-branch
+++ b/cr-daily-branch
@@ -186,6 +186,12 @@ if [ "x$REVISION_OVMF" = x ]; then
     fi
 fi
 if [ "x$REVISION_LIBVIRT" = x ]; then
+       case "$xenbranch" in
+       xen-[0-9]*-testing)
+               BASE_TAG_LIBVIRT=osstest/frozen/$xenbranch
+               export BASE_TAG_LIBVIRT
+               ;;
+       esac
        determine_version REVISION_LIBVIRT libvirt LIBVIRT
        export REVISION_LIBVIRT
 fi