登录 | 立即注册 切换到窄版
查看: 2889|回复: 0

应用软件自动发布的最佳实践

[复制链接]

18

主题

30

帖子

195

积分

版主

Rank: 7Rank: 7Rank: 7

积分
195
发表于 2017-2-11 09:00:09 | 显示全部楼层 |阅读模式
Best Practices forApplication Release Automation
应用软件自动发布的最佳实践
February 09,2017
Derek Langone
XebiaLabs
If you'rethinking about implementing Application Release Automation (ARA), here are sometips to get started:
您如果正在考虑实施应用软件自动发布(ARA),可以从下面一些技巧开始:
Startwith: Balancing the Art and Science of Application Release Management
从平衡应用发布管理的艺术性和科学性开始
■ Pick onesoftware project and map out all the steps in the release process, from designthrough production.
选取一个软件项目,从设计到生产过程中,把软件发布过程中的所有步骤都进行映射
■ Take aninventory of the DevOps tools use at each step of the above process.
理出一个清单,列出上述过程每个步骤需要使用的DevOps工具
■ Choose an ARAtool. When researching, look at multiple reference sources, from vendorinformation, to articles, to analyst reports. Gartner and Forrester both issued2016 reports that introduce ARA and evaluate key vendors in the space.
选择一款ARA工具。当寻找工具时,需要参考多包括厂商信息、发表文章、分析报告等种信息来源。Gartner和Forrester都在2016年发布了ARA简介和对该领域重要厂商的评估报告
■ Look for anARA solution that, at a minimum, integrates and orchestrates all your existingtools. if you have to manually connect every tool in the pipeline, you won't beable to scale.
找到一个ARA解决方案,它至少要求能够集成、编排你已经在用的工具。如果需要您手工衔接整个链条上的工具,那您就没法做到大规模扩展。
■ Besidesimplementing a good CI solution to automate your application builds, pick someareas in your release process to automate right away. For example, if you haveto update your ticketing system to denote that an application has been deployedto a staging environment, integrate your ARA tool to automatically update theticket with the appropriate deployment information.
在应用构建自动化中,除了实现一个良好的持续集成(CI)解决方案,还需要在您的发布流程中选择一些区域进行自动化。例如,在您更新工单系统,标识一个应用程序已经部署到准备环境中,需要集成ARA工具在工单系统自动更新合适的部署信息。
■ Train everyoneinvolved in the release process (including non-technical people) on how to usethe ARA tool, so each person understands how they can do their job in therelease process.
让所有人都融入发布过程中,包括非技术人员,因此每个人都明白他们在软件发布过程中自己能做哪些工作
■ Optimizingyour release process is like paying back a lot of credit cards: find yourbiggest bottlenecks and remove them first.
优化发布过程就像偿付大量的信用卡,找到最大的瓶颈并优先解决他
■ Determine somekey KPIs by which to measure success, such as time to delivery, deploymentfrequency, change volume, success rate and mean time to recovery.
确定一些关键指标(KPI),并度量这些指标来确定是否成功。例如交付时间、部署频率、变更容量、成功率和恢复时间等
Only after asingle team gets its first ARA project off the ground and running inproduction, should you start rolling out the new process and the ARA solutionto other teams. To encourage widespread adoption, it's important to show othersin the organization that the team was able to achieve its core success metrics.
只有在某个团队通过一个ARA项目落地,在生产环境中应用之后,再推出新的流程或为其他团队提供ARA解决方案。为了鼓励更大范围的使用,最主要是需要在组织中展现出整个团队能够在核心成功指标上获得提升。

翻译:Jim Chen

回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

QQ|Archiver|手机版|小黑屋|Ansible中国社区 ( 京ICP备13038968号

GMT+8, 2019-6-19 22:51 , Processed in 0.063913 second(s), 25 queries .

Powered by Discuz! X3.2

© 2001-2013 Comsenz Inc.

快速回复 返回顶部 返回列表