Repository navigation
Conversation
antonkri
requested review from
AlexanderLanin,
FScholPer,
MaximilianSoerenPollak,
PiotrKorkus,
dcalavrezo-qorix,
lurtz,
nradakovic,
opajonk and
pawelrutkaq
as code owners
October 14, 2026 10:39
antonkri
marked this pull request as draft
October 14, 2026 10:39
|
The created documentation from the pull request is available at: docu-html |
Image content is now split into three layers: the image itself (//images/<variant>), the deployed S-CORE platform (//deploy) and the showcases that demonstrate and verify it (//showcases). Before this change the two upper layers were mixed in both directions: the lifecycle showcase shipped the launch_manager and the standalone showcase shipped the config_daemon, while the persistency test scenarios binary was packaged with the platform applications. A showcase that ships the component it exercises verifies the binary it brought along instead of the one the distribution deployed, so a distribution failing to deploy an S-CORE module would still pass. - Add //deploy with one package per module (lifecycle, logging, communication, config_management) and the aggregate :platform_bundle / :platform_tar that every image consumes. - Move launch_manager and config_daemon from the showcases into //deploy; the showcase manifests now drive the deployed binaries. - Move the persistency test scenarios binary from the platform packaging into //showcases. - Fold images/common/apps into //deploy and point all images at the single platform bundle. - Document the layering and the layer 2 / layer 3 contract in deploy/README.md and in the platform integration guide.
The datarouter and mw::com configuration files lived under feature_integration_tests/configs/ but were never read by the feature integration tests. Their only consumers are the deployment packages and the ebclfsa image, so they belong next to the module they configure. Files move unchanged; the packaged paths stay /usr/bin/datarouter/etc/* and /etc/*. What remains in feature_integration_tests/configs is the test harness configuration (dlt_config_*, qemu_bridge_config).
Use score_pkg_bundle instead of a hand-written pkg_files. An alias keeps the installed binary name bin/cpp_tests_persistency, since score_pkg_bundle names binaries after their label.
antonkri
force-pushed
the
refactor/deployment-layering
branch
from
October 15, 2026 13:41
6fcf940 to
35929a6
Compare
The showcases are shipped in the QNX image, but only the ITF suite ran there, so none of them was ever executed on QNX. Run //platform_integration_tests:pit against the same QEMU image.
antonkri
force-pushed
the
refactor/deployment-layering
branch
from
October 15, 2026 14:07
35929a6 to
6c7ff63
Compare
This branch has not been deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Image content is now split into three layers: the image itself (//images/), the deployed S-CORE platform (//deploy) and the showcases that demonstrate and verify it (//showcases).
Before this change the two upper layers were mixed in both directions: the lifecycle showcase shipped the launch_manager and the standalone showcase shipped the config_daemon, while the persistency test scenarios binary was packaged with the platform applications. A showcase that ships the component it exercises verifies the binary it brought along instead of the one the distribution deployed, so a distribution failing to deploy an S-CORE module would still pass.