Skip to content
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

Investigate if splitting build steps into multiple build steps improves reusebility of the images #289

Open
tkilias opened this issue Jul 13, 2021 · 0 comments
Labels
feature Product feature

Comments

@tkilias
Copy link
Collaborator

tkilias commented Jul 13, 2021

Background

  • In (Add option to) Re-use images from a previous build run #245 was asked if we keep the docker build cache and if we can use it, that might be difficult
  • However, exaslct already provides a mechanism for reusing images, but in certain cases it might be too coarse.
  • Splitting up some build steps into multiple, might improve the reuse of images and with this, build speed.
  • A example could be, if we install apt packages, python packages and r packages in the same build step, we could split this into three build steps. We could put them in on Pipeline or use a diamond pattern, where we first install the apt packages, have then two build steps in parallel which install the python and r-packages and at last copy the updates into one images.
@tkilias tkilias added feature Product feature timeline:long-term Unlikely to be implemented in the near future source:external labels Jul 13, 2021
@redcatbear redcatbear removed the timeline:long-term Unlikely to be implemented in the near future label Apr 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Product feature
Projects
None yet
Development

No branches or pull requests

2 participants