[Starting] a large domestic bank continuous integration and delivery practices

I. Background

With the evolving architecture and micro technology in the service of our bank-depth application, issued by the complexity of application deployment greatly increased, publish operation and management of simple code configuration management, and artificial version of the manual recording mode deployment, low efficiency , operational risk, and therefore an urgent need to enhance the capacity of the Bank continued to deliver software as a whole, reduce operational risk application deployment release.
By introducing building automation and visualization software delivery pipeline integration from development, build, test, deploy, publish, operation and maintenance and other aspects, strengthening functional teams to assist and communicate the full realization of the project continued to build management automation.

Second, the implementation of the method

1. Overall architecture

DevOps is a set of software development teams can help greatly improve the models and best practices for the speed and quality of their software delivery composition; DevOps overall architecture is shown:

Use the main level from the association: development, testing and operation and maintenance team, matching the corresponding access control system.
From the aspects of the delivery process: covering the whole process from code to manage application delivery.
DevOps platform includes both project management, product management, delivery of macroscopic dimensions centers, organizations, etc., but also included in the compilation, deployment, and pass code management platform part, at the same time, the platform supports flexible mechanisms should be extended (such as extended tool integration, deployment capacity expansion, etc.), the face of complex scenes or special needs, the platform can also provide more flexible capacity.

2. Features

Feature will streamline management, quality management, alarm management, product management, project information management, system management, personal workstations and other modules, to deliver automated, visualized goals.

3. Continuous Integration

Continuous integration module main function code base management, build management and build definition instance management, DevOps platform build tasks can be divided into the following types:

• Demand type of task: jira, ones, etc.
• Compiled class task: Maven, Ant, and other front-end build
• Package type of task: Maven, ant, gradle, npm, docker, etc.
• Test class task: junit, Postman, Jmeter etc.
• Static code scanning: Sonarqube
• Security Scan: Xray
• Class deployment task: ansible, chef, shell
• Container classes: k8s, mesos
• Log class: elk
• Other tools tasks: shell, articles submitted to the nexus warehouse, Jfrog product libraries.
  Alternatively each construct define several tasks need to build, step by atomic arrangement, assembled into a complete build process, trigger a build (support gitlab, github, svn other common code base version management tool) when the code is submitted, such as binding jenkins, docker and other tools to enhance compilation speed flexible scheduling capabilities and enhanced resources, the continuous integration of the full link to get through, for example:
  

4. Continuous Deployment

Software teams often need to test different types of follow-up release pushed to different deployment environments discussed above.
For example, a common scenario is to deploy software to the test environment artificially QA testing, and then deployed to the performance test environment, automated load testing. If you build through the testing phase, the application may be deployed to a separate environment for UAT or beta testing later.
Other systems Ideally, candidates will publish any article and communicate reliably deployed into any environment this process should be automated as much as possible.
If companies want to continue at the speed of program delivery, it may take a day or multiple times a week, so it's working speed and reliability is essential.
Automated fashion between the mobile software environment as one of the main characteristics of DevOps team, so this is a key focus of DevOps.
Examples are as follows:

5. Technical Architecture

6. technologies, tools, roles, the ability to sort out

When Devops embodiment, techniques involved, tools, characters, combing ability as follows:

Third, earnings

A complete library Jfrog product procurement, on-line, high-availability open up the building and a tool chain around Jfrog product library; to achieve a continuous integration and continuous deployment capabilities, enhance product functionality, warehouse transfer function of different packages, package dependencies management, access visualization package metadata management and pilot projects;
the main benefits obtained as follows:
a unified product database management: a unified product database management software package, to change the original scattered everywhere, unable to trace problems traceable.
To simplify the steps: Before use, developers require manual deployment steps 7-10; after use, a key can be deployed to DEV, SIT, UAT environment.
Shorten the waiting time: testers can be deployed on demand, without waiting. Changed the situation in the past testers need to wait for developers to deploy.

** Please pay attention to more technology sharing JFrog Jay Frog online classroom
January 7, 20:00 online classroom: "Netflix, Oracle DevOps Road"
classroom benefits:

1. Oracle introduced during the difficulties encountered DevOps change
2. Solution
   3. floor DevOps used tool chain
   4. Oracle's self-CI / CD platform
   5.Netflix sustained delivery platform Spinnaker
   6. gains obtained after the completion of the transition DevOps
   Registration link: https://www.bagevent.com / event / 6321621
   sweepstakes:
   end of class five minutes, raffle
   first prize: Bluetooth headset millet
   second: JFrog new version of Jay frog T-shirt
   third: JFrog new version of Jay frog T-shirt
   **