An offline source code safe and continuous integration method

Abstract

The invention discloses a safe and continuous integration method for an offline source code. The method comprises the following steps: developing an on-site development source code; submitting the source code to svn or git; delivering the source code out of the database; using a maven construction program; using jenkins to carry out automatic deployment and automatic testing; carrying out testingin the party A delivery test environment; securely transferring the source code from the development site to the party A svn or git by using symmetric encryption and MD5 signature techniques; continuously integrating in a simulation test environment by using jenkins; informing operation and maintenance personnel of online increment version in the production environment, and ending. According to the offline source code safe and continuous integration method provided by the invention, an offline safe and continuous integration method is created, so that an advanced continuous integration technology of an Internet company can be applied to a high-level safety area of a power grid company, the demand response speed of a power service is increased, the software quality is ensured, and the integration risk is reduced.

Description

technical field [0001] The embodiment of the present invention relates to the technical field of automation, and in particular to a method for offline source code security continuous integration. Background technique [0002] With the rapid development of informatization in the power industry, before continuous integration is applied, the traditional development model is to divide the project into modules, and then integrate them together for testing after all codes are developed. With development, various software methods are flourishing, and the scale of software is also expanding. Power business requirements are becoming more and more complex, and changes are becoming more and more frequent. Software can no longer be developed simply by dividing modules. It requires mutual cooperation within the project. The disadvantages of this traditional model are becoming more and more obvious. Because many bugs existed in the early stage of the project, and the problems were not dis...

AI Technical Summary

Problems solved by technology

[0005] However, in large traditional state-owned enterprises such as power grid companies, most of the software development is mainly outsourced from other places, and the developers’ network cannot be connected with the network of the power grid company, so it is impossible to directly copy the existing continuous integration methods in the IT industry (such as figure 1 As shown), when it is necessary to quickly repair defects or change requirements, due to the developer's remote development, the development site and the implementation site environment are different, the system functions are becoming more and more complex, there are many versions, and the changes are frequent. The traditional software delivery method is not only uncontrollable. Moreover, the efficiency is low and the quality cannot be guaranteed

Images