10156 fast redeploy maven#12467
Open
ErykKul wants to merge 2 commits into
Open
Conversation
This comment has been minimized.
This comment has been minimized.
1 similar comment
|
📦 Pushed preview images as 🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Two related changes:
create-tables) on every deploy. A newConditionalSchemaCreatorsession-event listener creates missing entity tables at startup only when they are actually missing (empty DB or newly added entity), using the same EclipseLink schema framework. Flyway still runs on every startup as before.dev-*-frd.shshell scripts with anfrdMaven profile (mvn -Pfrd package) that hot-redeploys into the running container in ~10-15s, IDE/editor/platform independent. Adds on-demand metadata block + Solr schema updates from the working tree (dev_metadata_update) and raises the dev memory limit to 6 GiB to support repeated redeploys.Which issue(s) this PR closes:
Special notes for your reviewer:
Follow-up to #11961, per containerization-meeting feedback (no host bash, fix
persistence.xmlproperly, refresh metadata block TSVs). #11961's scripts were never in a tagged release, so the single release note describes the Maven workflow as new rather than as a replacement.Suggestions on how to test this:
mvn -Pct clean package docker:run, then edit a Java/XHTML file and runmvn -Pfrd package— change is live without a container restart, DB state preserved.@Entity, redeploy — its table is created automatically.docker start -a dev_metadata_update— block and Solr schema update.Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No.
Is there a release notes update needed for this change?:
Yes — included:
doc/release-notes/10156-fast-redeploy.md.Additional documentation:
Container guide updated: Fast Redeploy (Command-Line) section in
dev-usage.rst, plusconfigbaker-image.rstandsql-upgrade-scripts.rst.