|
|
At the time, since I was still a developer, I had no idea that in the near future I would be involved in what we call today. In this post, I'll describe the path we've taken as an organization and how my role has evolved in implementing best-in-class application development standards and hosting using practices, orchestration systems, and solutions. What it was like at the beginning of the journey Before describing the details of implementing individual solutions, it’s worth writing about the challenges we faced as an organization.
They can be described by two points: Fragmentation This is a well-known situation in the market and can be presented as an example of a system. In this case, the software creator builds a release version, which in the next phase the device manufacturer must adapt according to its system version as photo retouching well as graphics overlays, feature additions and other elements. As a result, it takes a considerable amount of time for the intended recipients to receive the software, since new versions of the system must be packaged with all the custom features of a given manufacturer and thoroughly tested. Our approach is similar.
On the master branch of the repository, we develop a base version of the platform, which then has to be merged into the client version. This resulted in conflicts, hundreds of manual tests, and the need for additional stability work. With this new approach, we are able to centralize developed code in a single repository using a trunk-based development approach and make the exact same software image available everywhere. Environmental Differences Another challenge is that at each stage of development, the software runs in a different environment.
|
|
發表於 2023-10-12 17:06:25