2 minutes to learn about docker

A list of environmental issues

The management of the test environment has always been one of the focuses of testers. Non-independent test environments cause a series of problems for testing, and the resource overhead of the test environment will also bring a lot of costs when there are too many teams, including:

1. Data independence: data interference between testers

two。 Environment independence: multi-branch parallel development, unable to quickly configure the same environment; unable to meet the distributed environment in specific scenarios

4.bug positioning: the development environment is not consistent with the test environment, resulting in higher communication costs for both sides to reproduce problems.

5. Automated testing / joint debugging testing: lack of a stable test environment for automation or joint debugging

6. Online problems: code omission, inconsistent environment configuration, building a high-cost quasi-production environment

7. Test cost: each set of environment requires human energy and new hardware resources.

The solution of docker

1. Testing: Docker is very suitable for test release. RD and FE students can encapsulate the Docker and provide it directly to testers to run, eliminating the need for testers to cooperate with OPS and developers to build and deploy the environment.

two。 Test data separation: in testing, it is often necessary to modify all kinds of dependent DB data due to the transformation of test scenarios. Docker can easily separate these data into different mirrors and switch them at any time according to different needs.

3. Easy to repeat the problem: the development and testing of the same configuration of the environment, there will no longer be rejected due to environmental differences of the bug;, while newcomers to the post can also quickly establish a development, compilation environment.

4. Expansion and migration service: increase and decrease the number of containers at any time according to the business request, on demand. Fast realization of second shift combined with ceph

5. Other: in the past, it took a lot of effort to tinker with new things to build an environment. Pull one from the public warehouse. Maybe it can be solved in a few minutes.

Environmental Management in docker era

After the transformation, what will happen to the process of software development and launch? Developers can push the code and dokcer build files to the code repository together, and the CI service will build a mirror image based on these files, and testers will pull the image to test and go online. Without much explanation, the illustration is as follows: