Customizing quartz config not working as expected

[tibcosoftware]

Customizing quartz config not working as expected

[bdurrow]

I'm not associated with TIBCO or Jaspersoft but I just started a project where I am deploying JasperReports Server to openshift 4.6. Based on my read of the included entrypoint.sh, it provides a way to apply customizations after the call to deploy-webapp-pro . Check out

js-docker/scripts/entrypoint.sh

Line 108 in cb49f87

apply_customizations() {

. Depending on the size of your customizations you could prepare a .zip and put them in a secret (configmaps have historically corrupted binaries such as zips) then mount that secret to ${MOUNTS_HOME}/customization or a directory identified by ${JRS_CUSTOMIZATION}. MOUNTS_HOME defaults to /usr/local/share/jasperserver-pro. If your customizations were too large to include in a secret you could put them into a PV. I prefer not to use a PV for this kind of data though because if the PV can't mount at startup it leads to service availability problems which is something we have had trouble with in the past. Another option is you can override the entrypoint to call a script you have added via configmap to stage the files to the customization directory from object store, nfs, version control or other network resource that is reliably available. Then at the end of the script exec PATH/TO/entrypoint.sh

If you have any helpful tips about deploying in Openshift I will gladly take them - I created a gist as a place to collect this info. Any contribution in the comments are appreciated.

[rreddyv-tibco]

We fixed the issue as part of this release https://github.com/TIBCOSoftware/js-docker/releases/tag/v4.1 and it will work as expected . Hence closing the issue.