官术网_书友最值得收藏!

Automating deployment

As you now, it is easier to write software in small chunks and deploy the new chunks as soon as possible, to make sure that they are working. To get there, companies practicing DevOps rely on continuous integration and continuous deployment pipelines. Whenever a new chunk of code is ready, the continuous integration pipeline kicks off. Through an automated testing system, the new code is run through all of the relevant, available tests. If the new code shows no obvious regression, it is considered valid and can be merged to the main code base. At that point, without further involvement from the developer, a new version of the service (or application) that includes those new changes will be created and handed off to a system called a continuous deployment system. The continuous deployment system will take the new builds and automatically deploy them to the different environments that are available. Depending on the complexity of the deployment pipeline, this might include a staging environment, an integration environment, and sometimes, a pre-production environment. Ultimately, if everything goes as planned (without any manual intervention), this new build will get deployed to production.

One aspect about practicing continuous integration and continuous deployment that often gets misunderstood is that new features don't have to be accessible to users as soon as they are developed. In this paradigm, developers heavily rely on feature flagging and dark launches. Essentially, whenever you develop new code and want to hide it from the end users, you set a flag in your service configuration to describe who gets access to the new feature, and how. At the engineering level, by dark launching a new feature this way, you can send production traffic to the service, but hide it from the UI, to see the impact it has on your database or on performance, for example. At the product level, you can decide to enable the new feature for only a small percentage of your users, to see if the new feature is working correctly and if the users who have access to the new feature are more engaged than the control group, for example.

主站蜘蛛池模板: 太谷县| 宝清县| 平阴县| 新邵县| 仁寿县| 西乌珠穆沁旗| 新安县| 桑植县| 大埔区| 浦北县| 城口县| 大安市| 长顺县| 尼勒克县| 泾川县| 富蕴县| 政和县| 六枝特区| 汉川市| 岱山县| 石泉县| 临武县| 格尔木市| 慈溪市| 阳朔县| 平乡县| 枝江市| 滨州市| 班戈县| 定州市| 如东县| 密山市| 朝阳区| 台湾省| 湘潭市| 桦川县| 中西区| 樟树市| 隆德县| 漠河县| 贵德县|