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 the build cache for the docker image is used in exalsct #189

Open
tkilias opened this issue Jul 13, 2021 · 0 comments
Open
Labels
refactoring Code improvement without behavior change

Comments

@tkilias
Copy link
Collaborator

tkilias commented Jul 13, 2021

Background

  • In (Add option to) Re-use images from a previous build run script-languages-release#245 was asked if we keep the docker build cache and if we can use it
  • When docker builds images each step in a Dockerfile produces an intermediate image which is kept in the build cache
  • Because, exaslct copies the build context to a temporary directory, we probably can't reuse these intermediate images, because Docker doesn't associate the new directory with a previous build
  • As such, keeping the build cache is likely not useful

Tasks

  • Investigate if the docker build cache can be used?
  • If it can't be used, check if we keep it.
  • If we keep it, change that.

Acceptance Criteria

  • Either, the build cache is used and improve the performance of rebuilds of a single images, or we remove the build cache after the build
@tkilias tkilias added the feature Product feature label Jul 13, 2021
@redcatbear redcatbear added refactoring Code improvement without behavior change and removed feature Product feature labels Dec 12, 2022
@redcatbear redcatbear transferred this issue from exasol/script-languages-release Apr 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Code improvement without behavior change
Projects
None yet
Development

No branches or pull requests

2 participants