Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: POLICY-4125
Change-Id: Id63b3badb1b451b36e3226970dcafaa5a62d860f
Signed-off-by: adheli.tavares <adheli.tavares@est.tech>
|
|
Issue-ID: POLICY-4529
Change-Id: I197a51892e9135d20c2e8a49ce7787df3bfbd4fa
Signed-off-by: adheli.tavares <adheli.tavares@est.tech>
|
|
Issue-ID: POLICY-4469
Change-Id: Ide93bd46e8452ddc7453b8ad8347cea6ec0144ac
Signed-off-by: adheli.tavares <adheli.tavares@est.tech>
|
|
Issue-ID: POLICY-4350
Change-Id: I2bbc47122aa5984fbe3f03edc252ea56e47dba73
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
The following improvements are added:
- "docker ps" command added to the wait_for_port.sh script
tp show status of the containers coming up and down
- "docker-compose logs" added to the end of the test runs
to print out the standard output from the containers
- Add standard output logging to all containers
- Some cleanup and use of better names
Issue-ID: POLICY-4350
Change-Id: I3ae8c59dba64f9c267f310366bb4a2a6ffd5d418
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
onap/policy-jdk-debian is only used by policy/drools
and policy/engine. Their corresponding Dockerfiles
remove the precreated $POLICY_HOME/etc/ssl in order
to proceed with their images build. In any case,
the directory layout under $POLICY_HOME should be handled
by its respective derived images.
Miscellaneous clean up of packages in the base image.
Some packages are only used in drools and not in engine,
hence removed and moved to drools. The python dependencies
(python 2) created issues with tooling (http and telemetry).
Issue-ID: POLICY-2181
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: I3028cc9aa10bb453110c45769a1dba0315f7704f
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
|
|
Issue-ID: POLICY-2088
Signed-off-by: Rashmi Pujar <rashmi.pujar@bell.ca>
Change-Id: Id06c467923b3df8c7199b349571676958341c2c5
|
|
Add multiplatfrom support for policy-base
and policy-common docker images:
- the pom.xml files are modified to push and pull from dockerhub instead
of nexus repository (as nexus lacks support for manifest list)
- for each image that is built with maven, an arch suffix is added to the
tag. The currently supported architectures are amd64 and arm64.
- the creation of the timestamped tag is moved from the pom.xml files to
the docker_push_manifest.sh script
- for each image built via the Jenkins CI jobs, the docker_push_manifest.sh
is called. The script pushes a manifest list for each tag, plus it
creates the timestamp tags for SNAPSHOT or STAGING images,
depending on what job called the script (merge job, or stag job)
For using the images, the name of the manifest list is to be used (which
is the same as the current images in nexus)
Issue-ID: POLICY-1997
Change-Id: If54e7ee6ac432a999844d3584e146a90e2247323
Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
change FEATURES_HOME variable assigment to allow
feature install (including healthcheck feature) in
docker image, change credential to be in line with
robot
Issue: POLICY-145
Change-Id: Ib7640e3947dab280f368531b693dc26e09fa6f21
Signed-off-by: Krzysztof Kwiecien <krzysztof.kwiecien1@orange.com>
|
|
Change-Id: I8cdbf98141070f89dd3c668a1aa3317fc9df2683
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Change-Id: I69f516128a3209c40441de568bac506b09f4ea45
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|