-
Notifications
You must be signed in to change notification settings - Fork 1.3k
optimize build of JB images #12296
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
optimize build of JB images #12296
Conversation
started the job as gitpod-build-ak-jb-backend-via-proxy.1 because the annotations in the pull request description changed |
7f550b7
to
a715f81
Compare
84ae1d3
to
f6f03d1
Compare
started the job as gitpod-build-ak-jb-backend-via-proxy.9 because the annotations in the pull request description changed |
/hold |
ℹ️ I'm reviewing it now! |
Maybe I broke images... Let me know if restarting did not help, then I have a look again. |
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.
In order to reuse downloads on changes to backend plugins.
1bb2f84
to
4d7195b
Compare
/unhold |
started the job as gitpod-build-ak-jb-backend-via-proxy.11 because the annotations in the pull request description changed |
Description
This PR separates download of JB backend from building JB images. It reduces the rebuild time to 15 mins instead of 25mins for the change of JB backend plugin.
Unfortunately copy step during image build gets invalidated for some reasons, so even we just change the backend plugin, copying of backend itself happens for all 8 images and it adds like 10 mins unnecessary. I will think later how to optimize father by probably decoupling deliver of plugins.
Related Issue(s)
Related to #12268
How to test
/hold
to remove test commit
Release Notes
Documentation
Werft options: