Red Hat Bugzilla – Bug 989460
It display blank page after add skip_maven_build marker to a jboss app & git push back
Last modified: 2016-10-30 18:53:33 EDT
Description of problem:
Add a skip_maven_build marker to a jboss app and then git push back, then access the app URL, it display blank page.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create a jboss app via jbosstool or rhc
2.Add skip_maven_build marker to the app
run `touch .openshift/markers/skip_maven_build`
3.git push & access the app URL
git push successfully & got blank page
git push successfully & app page display well
the status of the app is started
Closing this one.
When using skip_maven_build marker, the app developer must implement a new build or commit archived deployments to the Git repository. During the app create, a "default" WAR (which is analogous the product of a maven build using the default pom.xml provided with the app's Git template) is present. If you add the skip_maven_build marker without replacing the build system you're now skipping, the previously built (and now deleted) artifacts are never recreated.
Did you change this behavior? Because now, when I add a skip_maven_build marker and do git push, the app still displays the old (non-empty) content
With the new build/deploy system, previously built 'dependencies' (e.g. ROOT.war in the original QE example) are not purged unless force clean build is specified.
What happens when the app repo is cleaned and replaced from git and then re-deployed absent a Maven build is dependent upon the specific application details (e.g. if the app consisted of static resources not packaged by Maven, then skipping the Maven build wouldn't be expected to have any effect).
The system is working as designed, and so I'm closing this. Feel free to reach out on IRC or email with any further requests for clarification on the build/deploy behavior.