Critical When you create a release with HELM Charts for EAP (https://github.com/jbossas/eap-charts.git), two BuildConfig resources are created corresponding to the two steps of the chained build:
- first BuildConfig: for building the EAP based application inside the builder image (complete example in attached buildconfig-autoupgrading-app-build-artifacts.yaml)
- second BuildConfig: for deploying the EAP based application inside the runtime image (complete example in attached buildconfig-autoupgrading-app.yaml)
These BuildConfig just have the following triggers....
first BuildConfig:
triggers:
- type: ConfigChange
second BuildConfig:
triggers:
- type: ImageChange
imageChange:
from:
kind: ImageStreamTag
name: 'autoupgrading-app-build-artifacts:latest'
What's missing here, are the triggers that monitor the build image and runtime image streams for changes;
The triggers, in the proposed reproducer, should be:
first BuildConfig:
triggers:
- type: ConfigChange
- type: ImageChange
imageChange: {}
second BuildConfig:
triggers:
- type: ImageChange
imageChange:
from:
kind: ImageStreamTag
name: 'autoupgrading-app-build-artifacts:latest'
- type: ImageChange
imageChange:
from:
kind: ImageStreamTag
name: 'jboss-eap-8-tech-preview-eap8-openjdk17-runtime-openshift-rhel8:latest'
- relates to
-
JBEAP-25243 EAP 8.0 GA OpenShift Images Release
-
- Closed
-
