-
Notifications
You must be signed in to change notification settings - Fork 3
Use separate config files for unique spacecraft IDs in CI builds #68
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
base: main
Are you sure you want to change the base?
Conversation
- Convert ComCfg.fpp to template (ComCfg.fpp.in) - Add CMake option FPRIME_SPACECRAFT_ID (default 0x0044) - Configure ComCfg.fpp generation from template - Update CI to use spacecraft ID 0x00C1 - Add documentation for spacecraft ID configuration Co-authored-by: Mikefly123 <[email protected]>
Co-authored-by: Mikefly123 <[email protected]>
|
Instead create 2 ccsds file, if building in CI then sources += |
- Create ComCfg.CI.fpp for CI builds (spacecraft ID 0x00C1) - Keep ComCfg.fpp for development builds (spacecraft ID 0x0044) - Update CMakeLists.txt to select config based on CI env var - Remove template-based approach (ComCfg.fpp.in) - Simplify build process - no CMake options needed Co-authored-by: Mikefly123 <[email protected]>
Implemented your suggestion in commit dfd62b9. Now using two separate config files (ComCfg.fpp for dev, ComCfg.CI.fpp for CI) with conditional selection in CMakeLists.txt based on the CI environment variable. This is simpler and more maintainable than the template approach.
Done in commit dfd62b9. The new approach uses separate static config files instead of CMake template generation, which tightens the CI process by:
|
CI machines need unique spacecraft IDs to prevent command conflicts with development devices in shared lab environments.
Implementation
ComCfg.CI.fppfor CI builds (spacecraft ID0x00C1) and keptComCfg.fppfor development builds (spacecraft ID0x0044)CIenvironment variableBenefits
.fppconfiguration filesHow It Works
The build system automatically detects the environment via the
CIenvironment variable:CIis set) → usesComCfg.CI.fpp(spacecraft ID0x00C1)ComCfg.fpp(spacecraft ID0x0044)No additional build flags needed - it works automatically.
Development builds:
0x0044(68)CI builds:
0x00C1(193)Valid range: 10-bit CCSDS spacecraft ID (
0x0000-0x03FF)Original prompt
<issue_description>To prevent conflicting commanding from test devices in labs. Use a unique space craft ID for CI builds
proves-core-reference/FprimeZephyrReference/project/config/ComCfg.fpp
Line 18 in 1d53de9
Comments on the Issue (you are @copilot in this section)
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.