Short description:

For the introduction of Git into the further software development of a computing kernel, it is necessary to transfer the source code files from Git into the customer's source code management system, which has been leading until then.


For the import, it is necessary that changed files are recognized and identified in Git and transferred to the customer's own source code management system, since subsequent processes cannot be converted to Git.

Technical description:

In order for developers to be able to use Git, but still not disrupt the existing development and release processes, a bridge is needed from Git into the source code management system that has been used up to that point. This bridge must detect which files have been changed and import them into the source code management system with the appropriate meta information. To enable integration into the existing Jenkins infrastructure, the platform-independent implementation in Java is the obvious choice.