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

What images need to be re-built when which parts of the conf/config.yml are modified? #17

Open
SvenDowideit opened this issue Nov 29, 2021 · 1 comment

Comments

@SvenDowideit
Copy link

I see mention of running build.sh -S if the profiles are changed, but would like to know what needs doing if other parts of the file are changed.

And similarly, assuming that my build system is separate from my run time system, what non-image things need to be transferred - there's a lot of run time volumes, but its not entirely clear if they're just cache / run time data.

@brod-intel
Copy link
Contributor

./build.sh -S simply skips building ESP container services which have nothing to do with profile builds. The ESP containers only need to built be initially and when there is a new release of ESP repo.

./build.sh -S also means it will loop through conf/config.yml and sync all profiles then check profiles with "build" scripts. These build scripts perform pre-build process specifically. You use this feature if you want build a custom kernel, use debmirror to clone a distro on ESP, build source tarbal;s etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants