(chore) persist maven cache between builds #916
Conversation
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
|
I'm in a third-world country with very slow internet connections, so this feature would be extremely helpful. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Mounting the /usr/share/maven/ref/repository directory as a cache means that the m2 cache is preserved between subsequent invocations of
docker compose build, thus eliminating the need to re-download all the maven packages and openmrs modules. (SNAPSHOT versions of packages will still always be downloaded.)In a development environment, this can greatly speed up docker builds when trying out changes to the distro.
Incidentally, applying the same mounts to both the
mvn installandmvn cleancommands, for consistency.