Loading...

XML

Word

Printable

Blocked:
False
Ready:
False
Affects:

Documentation (Ref Guide, User Guide, etc.)
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Fix Build:
CR1
Release Note Text:
Undefined
Target Release:

7.9.1.GA
Git Pull Request:
https://github.com/jboss-container-images/jboss-kie-modules/pull/404, https://github.com/jboss-container-images/jboss-kie-modules/pull/405, https://github.com/jboss-container-images/rhpam-7-openshift-image/pull/482, https://github.com/jboss-container-images/rhpam-7-openshift-image/pull/483
[QE] How to address?:
---
[QE] Why QE missed?:
---
Market:

Sprint:
2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30)

The image does not use a PV to store it. It is using /home/jboss/.m2.

Projects that depend on other projects located in the same BC instance failed to build.

Every time BC is started you have to manually build each project on your Space.

This should be configurable with a flag so that users can determine the behaviour they desired.

By default .m2 persistence should be disabled.

incorporates

KIECLOUD-315 Allegedly BC's .m2 bug when deployed on OpenShift and pod (re)Started

is related to

RHPAM-3320 Business Central PV size is not configurable in Operator