@@ -54,7 +54,7 @@ xen-4.*-testing)
$TREE_XEN staging-$branchcore $LOCALREV_XEN
;;
xen-unstable-coverity)
- repo_tree_rev_fetch_git xen $TREE_XEN master $LOCALREV_XEN
+ repo_tree_rev_fetch_git xen $TREE_XEN smoked $LOCALREV_XEN
;;
qemu-mainline)
repo_tree_rev_fetch_git $branch \
@@ -60,7 +60,7 @@ xen-4.*-testing)
$TREE_XEN stable-$branchcore $LOCALREV_XEN
;;
xen-unstable-coverity)
- repo_tree_rev_fetch_git xen $TREE_XEN coverity-tested/master $LOCALREV_XEN
+ repo_tree_rev_fetch_git xen $TREE_XEN coverity-tested/smoked $LOCALREV_XEN
;;
qemu-mainline)
repo_tree_rev_fetch_git $branch \
@@ -70,7 +70,7 @@ xen-*-testing)
;;
xen-unstable-coverity)
cd $repos/xen
- git push $TREE_XEN $revision:refs/heads/coverity-tested/master
+ git push $TREE_XEN $revision:refs/heads/coverity-tested/smoked
;;
qemu-mainline)
cd $repos/qemu-mainline
In retrospect there isn't much point in defering coverity until the tree has been through a full test and it just results in potentially longer gaps between runs with larger numbers of commits included (for example the run on Sunday was skipped because master hadn't moved forward since Wednesday). Signed-off-by: Ian Campbell <ian.campbell@citrix.com> --- Deployment note, the existing coverity-tested/master branch should be renamed (git branch -m) to coverity-tested/smoked. --- ap-fetch-version | 2 +- ap-fetch-version-old | 2 +- ap-push | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)