ci: Rework SDK build steps #3586
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Significantly rework how we're doing the SDK step for our CI scripts: * Reduce the number of packages to speed up SDK build step. The only reusable piece of an SDK is the toolchain and it's own dependent pieces (i.e., sysroot dir), so don't waste time by building packages that will be rebuilt when the SDK is used. * Instead of always building the SDK based on witherspoon_defconfig, take into account the platform for which the SDK is being built for, but try to canonize it and consider it's primary characteristics to make it unique, such as buildroot version, architecture, OS, Kernel Headers and GCC version used. Without this, at the time of this commit, the complete zz_defconfig build is using GCC 7.4.0, the sdk build is using GCC 6.5.0 from witherspoon_defconfig - an inconsistency in the result from a complete versus an sdk-based build. Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Significantly rework how we're doing the SDK step for our CI scripts:
Reduce the number of packages to speed up SDK build step. The only
reusable piece of an SDK is the toolchain and it's own dependent
pieces (i.e., sysroot dir), so don't waste time by building packages
that will be rebuilt when the SDK is used.
Instead of always building the SDK based on witherspoon_defconfig,
take into account the platform for which the SDK is being built for,
but try to canonize it and consider it's primary characteristics to
make it unique, such as buildroot version, architecture, OS, Kernel
Headers and GCC version used.
Without this, at the time of this commit, the complete zz_defconfig
build is using GCC 7.4.0, the sdk build is using GCC 6.5.0 from
witherspoon_defconfig - an inconsistency in the result from a
complete versus an sdk-based build.
Signed-off-by: Klaus Heinrich Kiwi klaus@linux.vnet.ibm.com