If one downloads the nightly add-ons.zip build, for example:
rhdm-7.1.0.DM-redhat-20180829-add-ons.zip
, you will find in it (among other archives), the both rhdm-7.1-controller-ee7.zip and rhdm-7.1-employee-rostering.zip.

Packages inside the rhdm-7.1-controller-ee7.zip is a very simple controller.war directory, and a SecurityPolicy directory. Given that the names of these do not change, it is easy to upgrade the production openshift image builds without having to complicate the scripts that do so.

However, the rhdm-7.1-employee-rostering.zip packaging structure is very different, and overly complicated. Instead of a simple employee-rostering.war file or directory (preferred so we can do META-INF and WEB-INF config file filtering more easily), one has to navigate down into the employee-rostering-distribution-7.11.0.redhat-20180829/binaries/ directory, and look for the employee-rostering-webapp-7.11.0.redhat-20180829.war file. This complicates production image build scripts.

The structure should be the same as the controller's. Specifically, inside rhdm-7.1-employee-rostering.zip, there should be a very simply named employee-rostering.war file or directory, and if required (and is now simply just missing), a SecurityPolicy directory too.

So to recap, this is bad:

• rhdm-7.1.0.DM-redhat-20180829-add-ons.zip!/rhdm-7.1-employee-rostering.zip!/employee-rostering.war/employee-rostering-distribution-7.11.0.redhat-20180829/binaries/employee-rostering-webapp-7.11.0.redhat-20180829.war

But this is good:

• rhdm-7.1.0.DM-redhat-20180829-add-ons.zip!/rhdm-7.1-controller-ee7.zip!/controller.war/
• rhdm-7.1.0.DM-redhat-20180829-add-ons.zip!/rhdm-7.1-employee-rostering.zip!/employee-rostering.war/