OPTF-Refactor CLM project block
The clm job portion needs to be on its own
project section similar to the Sonar portion.
The reason behind this, is because we only want
this job to be running for master and no other
branches. Also, this is in preparation for the
work that is to come from global-jjb on application
names in CLM.
Change-Id: If4e6bc2643f8ef1f0c57b8ff737261b7e65e7fe0
Issue-ID: CIMAN-213
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
diff --git a/jjb/optf/optf-osdf.yaml b/jjb/optf/optf-osdf.yaml
index 8cc048d..6c6e2fc 100644
--- a/jjb/optf/optf-osdf.yaml
+++ b/jjb/optf/optf-osdf.yaml
@@ -15,7 +15,6 @@
pattern: '**'
pom: 'pom.xml'
jobs:
- - gerrit-maven-clm
- '{project-name}-{stream}-{subproject}-verify-python'
- '{project-name}-{stream}-{subproject}-verify-java'
- '{project-name}-{stream}-{subproject}-merge-java'
@@ -67,3 +66,12 @@
mvn-settings: 'optf-osdf-settings'
mvn-goals: 'clean install'
mvn-opts: '-Xmx1024m -XX:MaxPermSize=256m'
+
+- project:
+ name: optf-osdf-clm
+ jobs:
+ - gerrit-maven-clm
+ project: optf/osdf
+ project-name: 'optf-osdf'
+ branch: 'master'
+ mvn-settings: 'optf-osdf-settings'