You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've added a stage "stage2a" which adds application specific things to the RPi OS Lite image (created by stage2). I want to create mutiple builds (optimally from a build pipeline) which only differ in the stage2a stage, meaning that everything up to stage2 remains unchanged.
Every stage starting from stage3 has SKIP and SKIP_IMAGE files in it so that the build process stops after stage2a. This works good.
However, when running multiple builds sequencially, stage1 and stage2 are never "cached" and rebuilt, which takes a lot of time. So my question is: Is there a way to cache build stages up to a specific stage to speed up multiple builds?. I'm using the docker build method (./build-docker.sh).
Edit: The instuctions in the README ("Skipping stages to speed up development") does not work for me. What I've tried (the correct stages already have SKIP_IMAGE files):
But wouldn't that mean that a stage n+1 would include all changes made in stage n? I want to make e.g. five images, all with "unique" settings starting from stage 2 (Lite image).
I've added a stage "stage2a" which adds application specific things to the RPi OS Lite image (created by stage2). I want to create mutiple builds (optimally from a build pipeline) which only differ in the stage2a stage, meaning that everything up to stage2 remains unchanged.
Every stage starting from stage3 has
SKIP
andSKIP_IMAGE
files in it so that the build process stops after stage2a. This works good.However, when running multiple builds sequencially, stage1 and stage2 are never "cached" and rebuilt, which takes a lot of time. So my question is: Is there a way to cache build stages up to a specific stage to speed up multiple builds?. I'm using the docker build method (
./build-docker.sh
).Edit: The instuctions in the README ("Skipping stages to speed up development") does not work for me. What I've tried (the correct stages already have
SKIP_IMAGE
files):./build-docker.sh # builds all stages touch stage1/SKIP touch stage2/SKIP PRESERVE_CONTAINER=1 CONTINUE=1 CLEAN=1 ./build-docker.sh
Both
./build-docker.sh
calls run all build stages. Am I doing anything wrong?The text was updated successfully, but these errors were encountered: