Found three merge jobs still using git-scm-gerrit 61/27761/1
authorAric Gardner <agardner@linuxfoundation.org>
Mon, 30 Jan 2017 21:34:06 +0000 (16:34 -0500)
committerAric Gardner <agardner@linuxfoundation.org>
Mon, 30 Jan 2017 21:34:06 +0000 (16:34 -0500)
merge jobs should not be cloning the patchset, they should be cloning
master after the merge is complete.

Change-Id: I3cd853c16bdc2533e8fb926eeea8926f8fc7ac04
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
jjb/daisy4nfv/daisy4nfv-merge-jobs.yml
jjb/escalator/escalator.yml
jjb/releng/opnfv-docs.yml

index d84e46f..1e7bf90 100644 (file)
@@ -50,7 +50,7 @@
             option: 'project'
 
     scm:
-        - git-scm-gerrit
+        - git-scm
 
     wrappers:
         - ssh-agent-wrapper
             block-level: 'NODE'
 
     scm:
-        - git-scm-gerrit
+        - git-scm
 
     wrappers:
         - ssh-agent-wrapper
index 31e0c00..103a696 100644 (file)
     concurrent: true
 
     scm:
-        - git-scm-gerrit
+        - git-scm
 
     wrappers:
         - ssh-agent-wrapper
index f6092ee..6224ca9 100644 (file)
@@ -89,7 +89,7 @@
             description: "JJB configured GERRIT_REFSPEC parameter"
 
     scm:
-        - git-scm-gerrit
+        - git-scm
 
     triggers:
         - gerrit: