Pin kernel and uboot to stable release revision #9
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
Upstream uses AUTOREV and this causes two problems: - we don't know which revision has been used by which balenaOS release - automated Jenkins builds sometimes break when upstream performs changes and we can't easily determine the window in which the changes have been performed We thus pin the SRC_REV to the revision used when the device has been integrated with balenaOS, as per the upstream relese tag xml Changelog-entry: u-boot: Pin SRC_REV to the one present at the integration date Signed-off-by: Alexandru Costache <[email protected]>
Upstream uses AUTOREV and this causes two problems:
- we don't know which revision has been used by which
balenaOS release
- automated Jenkins builds sometimes break when upstream performs changes
and we can't easily determine the window in which the changes
have been performed
We thus pin the SRC_REV to the revision used when the device has
been integrated with balenaOS, as per the upstream relese tag xml
and will update it when necessary or when we update the BSP to
another stable version.
Signed-off-by: Alexandru Costache <[email protected]>
acostach
force-pushed
the
pin_kernel_and_uboot
branch
from
dd12256 to
75053d2
Compare
Changelog-entry: layers/meta-balena: Update to v4.0.29 Signed-off-by: Alexandru Costache <[email protected]>
Signed-off-by: Alexandru Costache <[email protected]>
This reverts commit 3fadcc2. because Autokit tests passed with the smaller rootfs size and the timeout can now be investigated and tackled in leviathan. Signed-off-by: Alexandru Costache <[email protected]>
|
@balena-ci I self-certify! |
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.
Pin SRC_REV to the one used at the integration date
Upstream uses AUTOREV and this causes two problems:
balenaOS release
and we can't easily determine the window in which the changes
have been performed
We thus pin the SRC_REV to the revision used when the device has
been integrated with balenaOS, as per the upstream relese tag xml