Application of Continuous Integration (CI)

1. Introduction
Beijing Hunk Times Technology Co., Ltd. provides solutions in professional IT service, focusing on software research and development, integrated services, answers, and IT services in the Internet, financial industry, energy manufacturing, and other industries. Kindness, good industry reputation, and professional attitude have accumulated several specific industry solutions and best practices.
As a typical practice in financial institutions, continuous integration (CI) was born to improve the efficiency of product development and testing, allowing the team to receive constant feedback and make continuous improvements.
2. Overview of Continuous Integration
3. Three steps to build a primary environment
Requirements confirmation, work order submission, environmental preparation.
4. Three steps to complete continuous integration
A. Project library establishment
After the requirements are confirmed, the person in charge of R&D establishes a project library:
1. Development and test The development branch corresponds to the development and test environment
2. Integration test The test environment of the unit (interface) corresponding to the unit branch
3. User test The integrated branch corresponds to the integrated test environment
4. The mainline corresponds to the production environment

B. Code merger
1. Developers do development on the development environment, and self-test is completed, they are merged into the integration test branch.
2. The tester completes the unit test on the integration test line. After passing the test, the developer merges the code from the integration test branch to the user test branch.
3. Testers do integration tests on the user test line. After the integration test passes, Teamlear merges the code from the user test branch to the master production line.
C. Job construction
1. Development, integration, and user testing are three jobs: development, integration, and user testing.
2. Three test jobs are triggered according to internal requirements to achieve the three steps of compilation, packaging, and deployment to the test environment. Position can be set to be activated automatically or manually.
3. Account is a production job, and the person in charge of the project is responsible for compiling, packaging, and publishing the rpm package to the Yum warehouse. It is used for operation and maintenance online, and it is triggered manually.

Previous：won the bid for the State Grid Project

Next：won the bid for of blockchain node project