On Fri, 31 Jul 2015, Ian Jackson wrote:
> Stefano Stabellini writes ("[PATCH v8 2/2] OSSTest: push successful raisin
> builds"):
> > Determine the most recent raisin revision that needs to be tested,
> > by comparing the staging with the master branches. Push to
> > raisin.git:master when the build is successful.
> >
> > Do not run any jobs on the raisin flight.
>
> The raisin flight should probably lack most of the other build jobs,
> too ?
Yes, that's right. I think that the following, part of the first patch,
should already take care of that?
diff --git a/mfi-common b/mfi-common
index 16fc8c5..8d6ab3e 100644
--- a/mfi-common
+++ b/mfi-common
@@ -148,6 +148,17 @@ create_build_jobs () {
*) enable_ovmf=true;
esac
+ case "$xenbranch" in
+ xen-3.*-testing) enable_raisin=false;;
+ xen-4.[0-5]-testing) enable_raisin=false;;
+ *) enable_raisin=true;
+ esac
+ case "$branch" in
+ xen*) ;;
+ *) enable_raisin=false;;
+ esac
+
+
eval "
arch_runvars=\"\$ARCH_RUNVARS_$arch\"
"
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
