-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Resolve bwc dependencies for packer cache #125625
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
bwc builds are build against an empty Gradle userhome by now and this results in - downloading the gradle distro for each first bwc build - downloading build dependency on each fresh bwc build resulting in >1gb of dependencies resolved - downloading java toolchains not resolved otherwise on the first bwc build.
|
Pinging @elastic/es-delivery (Team:Delivery) |
| * for packer caching only | ||
| * see CacheCacheableTestFixtures. | ||
| * */ | ||
| protected MinioTestContainer() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixes another packer cache issue when caching docker images we rely on in our fixtures: https://buildkite.com/elastic/elasticsearch-vm-images/builds/671#0195c53c-d566-405c-9503-afc95a6e6706
|
We can track the impact of better bwc caching basically by using this GE view: https://gradle-enterprise.elastic.co/scans/performance?search.relativeStartTime=P28D&search.rootProjectNames=elasticsearch&search.tasks=extractedAssemble&search.timeZoneId=Europe%2FVienna |
💚 Backport successful
|
bwc builds are built against an empty Gradle userhome by now and this results in
Requiring less downloads on every ci build also results in more stable builds with less transient download errors like: https://gradle-enterprise.elastic.co/s/wcp3lfhkkhrqg/console-log/task/:distribution:bwc:staged:buildBwcLinuxTar?anchor=744&page=1