POLICY-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: I7f4c631fb4b91cfd050f2cf8926e169e75812bd6
Issue-ID: CIMAN-213
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
diff --git a/jjb/policy/policy-engine.yaml b/jjb/policy/policy-engine.yaml
index f116f7b..0dc51b1 100644
--- a/jjb/policy/policy-engine.yaml
+++ b/jjb/policy/policy-engine.yaml
@@ -3,8 +3,6 @@
name: policy-engine
project-name: 'policy-engine'
jobs:
- - gerrit-maven-clm:
- build-timeout: 30
- '{project-name}-{stream}-verify-java'
- '{project-name}-{stream}-merge-scm-mvn-script':
mvn-goals: 'clean deploy -B
@@ -40,3 +38,13 @@
mvn-settings: 'policy-engine-settings'
mvn-goals: 'clean install'
mvn-opts: '-Xmx1024m -XX:MaxPermSize=256m'
+
+- project:
+ name: policy-engine-clm
+ jobs:
+ - gerrit-maven-clm:
+ build-timeout: 30
+ project: policy/engine
+ project-name: 'policy-engine'
+ branch: 'master'
+ mvn-settings: 'policy-engine-settings'