It operates in the agile R&D mode and combines it with Java language development. The product architecture includes background services, front-end Web and APP, and features of multiple software components. The entire product is planned for R&D applications in demand management, feature story management, code hosting, and continuous Construction, automated testing, version release, fault management, and so on have all made appropriate specification requirements and conventions and quickly established a complete set of DevOps tool chain support.
ã€Key words】
DevOps, Docker, Cloud CI, Product Library, Automated Testing, Metrics
[Tool Chain Introduction]
The entire product planning R&D application uses a sequence of tool chain support:
1) The original demand is entered into the original demand management system by users closest to the market and collected and analyzed by the planning team to form a formal product requirement.
2) After the product requirements are entered into the demand management system, the demand analysts organize the demand instantiation analysis, and complete the decomposition of the demand-to-feature and story tasks online.
3) The characteristic story tasks to be implemented in the demand management system are evaluated by the development team and incorporated into the iterative development plan. The developers develop the code, and after the code review, story feature test, and BA acceptance, the online status changes to development completion.
4) The code hosting uses the Gerrit system, compiles and builds using the cloud CI system, the code static check uses the Klockwork cloud inspection system, the version uses the product library management, and the automated test access cloud test management system.
5) The entire product R&D process uses Wiki for product R&D applications and collaborative information sharing management for each team. The information access measurement system at each stage performs measurement analysis and information sharing display.
ã€Practices】
DevOps Several Important Support Tools Diagrams
Code library migration:
The SVN migrates to Gerrit. The benefits of using Gerrit migration include:
1. In addition to creating sub-libraries and configuring sub-library access permission groups, administrators need to configure the operation. The frequently-used sub-library access rights members are added or subtracted to the team's own decision. The previous SVN authority management approval process is longer. problem.
2. The speed of single-bank download increases more, about 10 times the rate.
3. The code size statistics and measurement system interface is simple, and can quickly push the metric system configuration personal code size statistics and statistical results emails to the project group automatically.
4. The company-level Gerrit code hosting is more efficient and secure.
Cloud CI deployment uses:
The Jenkins-based CI service provided by DevOps has a huge amount of resources for the project to achieve high concurrency scheduling, so that the project does not have to care about the underlying resources and only focuses on the business itself.
Code Klockwork static check:
The project development language is mainly Java. The Klockwork tool is used to perform static scan checks on Java code. Klockwork static inspection is divided into two steps:
1. Before the developer coded the archived code, the newly added code was scanned locally by the Klockwork plug-in integrated into the Eclipse development environment. After the alarm was cleared, it was archived on Gerrit. The project agreed that Klockwork alarms discovered after archiving the code into the Gerrit library were treated as developer leaks. KW Native Java Code Scanning Alarm Elimination Configuration See "Klocwork Eclipse Plug-in Installation and Use."
2. The project deploys cloud KW scans, performs daily static scans of project codes, and finds that the alarm information is pushed to the project team. Daily KW scan email push results.
Release Management:
After the development team develops the completed version according to the version plan, it releases different versions of the delivery version to the version requester. The historical release version is recorded to the version release management system, which enables retrospective query and version application management. The release version delivered by the development team is divided into project internal integrated version, external integrated version, internal acceptance version, external acceptance version, formal commercial version, experimental oriented version, user trial version, and commercial patch version. According to the external relationship collaboration and the upstream and downstream delivery processes, different versions are released at different times to meet the needs of all parties. The various types of versions released externally by the development team are recorded in the version release management database and can support query of historical version information. The historical version information is measured and counted, making it easy for internal and external stakeholders to obtain version-related information and reduce version-related information communication. Cost, improve the management efficiency of DevOps chain in the delivery version.
External fault tracking management:
In view of the fact that the external application surface of the product is widely distributed and external fault information is collected and tracked in a difficult situation, the external fault management tracking function of the demand development management system is used. The user directly enters external issues into the demand development management system and pushes the mail to the project R&D team automatically. Carry out follow-up processing and automatically push problem resolution progress to external stakeholders. As shown below:
Collaboration and metrics:
The Wiki system is used to transfer and share information among project teams, and the metrics information is composed of different dimensions of R&D, such as the measurement system push project team and members.
Measurement system applications:
The R&D process is linked to the measurement system. The indicators of the R&D process in each stage are aggregated and analyzed by the measurement system and pushed to the project team. Metrics display description:
Measure system application greatly improves the efficiency of timely understanding of all aspects of the team's metrics at all stages of the R&D process, freeing the human resources from the statistics of human metrics, and making metrics more flexible, faster, and automated.
ã€Evaluation】
The project has a complete set of DevOps end-to-end application practices, which will play an active role in improving project R&D efficiency and quickly and easily implementing information sharing. Demand management lines support demand analysis, iterative development, and version delivery processes using the original demand management system and demand development management systems. Gerrit, Cloud CI, Cloud KW, product library, cloud testing, and version release management support management from various stages of code management, version build, static checking, version management, automated testing, and release management.
[DevOps Toolchain Improvement Suggestions]
1. The original demand management system system is connected with the downstream demand analysis management system.
2. Cloud KW incremental code scan result push will introduce KW alarms to individuals.
3. Cloud test enhancements Analyze format conversion compatibility support for third-party test tool reports to facilitate access to more automated test details.
4. When there are many metric system configuration items, scrolling up and down is more difficult, and it is recommended to add the next level of classification.
5. There is no correlation between the pop-up dialog box and the scroll bar position on the right side of the measurement system. It is recommended that the pop-up dialog box be displayed at the current position of the scroll bar.
6. The filtering conditions of the measurement system indicator items are too simple. It is inconvenient for the calculation to filter yesterday's data.
7. Cloud KW scanning rules need to be easily configured and modified.
The material of this product is PC+ABS. All condition of our product is 100% brand new. OEM and ODM are avaliable of our products for your need. We also can produce the goods according to your specific requirement.
Our products built with input/output overvoltage protection, input/output overcurrent protection, over temperature protection, over power protection and short circuit protection. You can send more details of this product, so that we can offer best service to you!
Led Adapter,Mini Led Adapter,Security Led Adapter,Waterproof Led Adapter
Shenzhen Waweis Technology Co., Ltd. , https://www.laptopsasdapter.com