buildkite: pre-fetch system-test maven deps on host before container [MERGEOK]#37045
Merged
Conversation
…build Run `mvn dependency:go-offline` against docker/vespa-systemtests/tests/pom.xml on the build host, before the system-test container is built and the host's ~/.m2/repository is copied into docker/maven-repo as the container's offline repo. Why: doing this on the host (instead of inside the container) populates the persistent ~/.m2 cache on the build agent, so subsequent Buildkite runs reuse the downloaded artifacts instead of re-fetching them every time.
esolitos
previously approved these changes
May 28, 2026
esolitos
changed the title
hmusum
approved these changes
May 28, 2026
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
3 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.
…build
Run
mvn dependency:go-offlineagainst docker/vespa-systemtests/tests/pom.xml on the build host, before the system-test container is built and the host's ~/.m2/repository is copied into docker/maven-repo as the container's offline repo.Why: doing this on the host (instead of inside the container) populates the persistent ~/.m2 cache on the build agent, so subsequent Buildkite runs reuse the downloaded artifacts instead of re-fetching them every time.