DevOps based migration aspects from Legacy Version Control System to Advanced Distributed VCS for deploying Micro-services

Out of all version control system existed in development world, now a days 79% version control systems are on Git and it’s growing. Many organizations have already left older version control system and adopted Git as their VCS. Although there are some migration tools available in the software industry, their options are somewhat lacking, especially when it comes to pre-migration checks such as empty directories, failover capability and reporting as steps of post-migration. In this work, various aspects of the migration work are explored within the sort of problems and their respective solutions. Four migration aspects - Project structure validation and self-resiliency capabilities, Sensing the SVN & Git SSH network connectivity using NodeMCU IoT platform, SVN users and Git author mapping pattern validation, Remote Git server filing system & space pre-validation - are covered in this work along with possible solutions. Various DevOps systems for version control migration are investigated like Kubernetes, AppDynamics, Chef, Jenkins. It is observed that current legacy migration DevOps tools do not provide the direct solutions for the version control migration like software project structure validation and self-resiliency approach but they indirectly speedup the migration by providing infrastructure provisioning, validation, monitoring and scaleup/down as and when required. It means no single migration tool pre-check that if the software project structure is 100% compatible for Git server and if there’s any discrepancy then automatically correct that structure. One of the main aims of DevOps is to bridge the gap between Business, Dev and IT with the aim of converting the SDLC into a strategic resource for the firm. However, to achieve this goal, it is imperative to choose the right tools.