Version control for Yocto Source Mirror
Peltonen, Pauli (2022)
Peltonen, Pauli
2022
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2022060113931
https://urn.fi/URN:NBN:fi:amk-2022060113931
Tiivistelmä
Version controlling one’s work has become the norm. However, there can be cases where no version control system exists or the system in place is inadequate for the requirements of the work. This thesis aims to implement a version control system for aproject commissioned by Neuro Event Labs Oy. The thesis objective was to evaluate, develop, and implement a suitable version control system for the purpose of tracking, archiving, and backing up source code packages used in Linux image building. This research is part of a project done in Neuro Event Labs Oy to improve the traceability of an increasing number of source code packages.
The project work started with defining the specific needs this project has for version control. Next, research and literary review were conducted to discern what type of approach should be taken to satisfy the determined criteria. Various options for version control systems were considered and Git Large File Storage was chosen as the core tool for the system. After the suitable tool was chosen, a script was created to automatically identify newly added source code packages and to recognize when pre-existing packages were out of date or otherwise no longer used by the build environment. According to the new process flow, a backup of the version-controlled source mirror is occasionally taken.
The project work started with defining the specific needs this project has for version control. Next, research and literary review were conducted to discern what type of approach should be taken to satisfy the determined criteria. Various options for version control systems were considered and Git Large File Storage was chosen as the core tool for the system. After the suitable tool was chosen, a script was created to automatically identify newly added source code packages and to recognize when pre-existing packages were out of date or otherwise no longer used by the build environment. According to the new process flow, a backup of the version-controlled source mirror is occasionally taken.