You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found out the issue is related to the pipeline defined in cicd-template.yaml from https://github.com/OpenShiftDemos/openshift-cd-demo. The Jenkinsfile 'Deploy DEV' stage is not placing creating the configuration directory (containing the users/roles) into the right directory structure within the oc-build directory. This is where the WAR is copied to and the configuration directory needs to be at the same level for the binary build to work as expected and place the configuration files in the right EAP_HOME/standalone/configuration directory within the container.
Activity
karstengresch commentedon Apr 4, 2017
As the md5 of redhat1! is
c4df094e0bf5bc1c471423c4f356e902
on several *ix-systems tested, I assume the password in the documentation is not correct.
abessifi commentedon May 22, 2017
Same issue here!
redlumxn commentedon Jun 12, 2017
Found out the issue is related to the pipeline defined in
cicd-template.yamlfrom https://github.com/OpenShiftDemos/openshift-cd-demo. The Jenkinsfile 'Deploy DEV' stage is not placing creating the configuration directory (containing the users/roles) into the right directory structure within theoc-builddirectory. This is where the WAR is copied to and the configuration directory needs to be at the same level for the binary build to work as expected and place the configuration files in the rightEAP_HOME/standalone/configurationdirectory within the container.oc-build
----ROOT.war
----configuration
--------application-roles.properties
--------application-users.properties
I simply changed the Jenkinsfile DEV stage from:
to
Hope this helps
rafaeltuelho commentedon Aug 20, 2018
@redlumxn send a PR for this! ;-)