policy/docker does not need to be built 87/43587/1
authorJorge Hernandez <jh1730@att.com>
Wed, 18 Apr 2018 18:10:33 +0000 (13:10 -0500)
committerJorge Hernandez <jh1730@att.com>
Wed, 18 Apr 2018 18:14:34 +0000 (13:14 -0500)
commit2ddc0d92fbacd6293ac5699d6ed84291e23dd92b
treeca633ab955f0cf35f5fb7aee86b4f65b014467dd
parent2be508ad078dd50e167885500095c51a9af83cf9
policy/docker does not need to be built

This is a companion review to
https://gerrit.onap.org/r/#/c/43585/

the policy/docker project does not need to
be built any longer as it does not produce any
delivery artifacts, therefore it does not need
any Jenkins jobs.  Instead, it is used as
configuration for policy docker-compose based
heat based installations.

Change-Id: Ic22b8163bd52e21a3d3ece1ca81b113ca5e8f352
Issue-ID: POLICY-737
Signed-off-by: Jorge Hernandez <jh1730@att.com>
jjb/policy/policy-docker.yaml [deleted file]