-
Notifications
You must be signed in to change notification settings - Fork 350
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
Bugfix/5758 incremental image build fix #5772
Bugfix/5758 incremental image build fix #5772
Conversation
✔️ Unit test coverage report - coverage increased from 42.9% to 43% (+0.1%) |
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.
LGTM. Nice work, thanks!
0fa293d
to
b8d5acf
Compare
✔️ Unit test coverage report - coverage increased from 42.9% to 43% (+0.1%) |
… compatible with the incremental image build algorithm
b8d5acf
to
db8c0fa
Compare
I see some e2e tests have failed. I'm trying to run the failed tests locally to see what needs to be fixed, but this will probably take some time... |
ec7d931
to
7ef2d96
Compare
…application jar when matching dependencies
7ef2d96
to
b9bf1be
Compare
Added b9bf1be to the PR. The image reuse algorithm was considering the application jar file as a dependency. As each integration generates its own jar file with the same name, but different checksum, there would never be a match and we would always use the root image as base. |
This is a proposal for solving the bug reported in #5758.
The main idea is that the incremental image build algorithm will select the base image that has more dependencies among those required by the new image, but no extra ones.
Also, the logic in build_type_support.go has changed to be compatible with this approach. The matching build will be the one with more common dependencies, but no extra ones.
Closes #5758
Once approved, I can backport this to release-4.x as well.
Release Note