Example tools.xml segger embedded studio5/20/2023 ![]() There can also be advantages to placing each layer of the application into different repositories as well. ![]() The advantage to this is that if configuration changes are needed for a SKU or a specific customer, it doesn’t force changes to the application that could accidentally propagate to other systems.Ĭonfiguration is not the only component that can benefit from being placed in a separate repo. At a minimum, this creates the core product code and several configuration repos that manage how the core application will behave. Therefore, teams can carefully examine their product’s design and place all configuration code into a separate repository. In many cases, a products code will be used across multiple product SKUs and, for a decade or more, may find different configurations to meet customer requirements. After all, it’s one product, and shouldn’t everything for the product be contained in one place? I would argue, NO! Breaking the application into multiple repositories can dramatically improve codebase configuration management. When working on an embedded product, it can be tempting to place all the code for a product into a single version control repository. In this post, we will explore three tips for embedded software configuration management that I have found to simplify configuration and minimize technical debt over a product’s lifetime. These systems require the ability to be easily configured so that the code does not become a nightmare and minimize the chances of improperly configuring them. ![]() Systems today are often designed to work in multiple products, for various customers, over long-time frames. ![]() Embedded software configuration management can be a tricky endeavor. ![]()
0 Comments
Leave a Reply. |