识别DevOps的最佳实践（以及如何实施）

在未经训练的眼睛上，Devops看起来像是”一个大的Wibbly Wobbly的球……时光薄荷…东西。" But it's so much more than that. DevOps is a powerhouse, combining technology and people to create impressive products, services, and software solutions.

但是，为了充分利用DevOps Workflow，您需要最大程度地利用其提供的所有功能。在这个方面，这篇文章将涵盖运行团队的一些最佳实践DevOps pipelineand workflow.

Best Practices for DevOps

DevOps的许多最佳实践围绕使用合适的工具来围绕着工作。但是，不仅如此。文化和实践等许多因素会影响最佳实践。考虑到这一点，这些实践将更多地以一般概述的方式进行。

1. Implement version control workflow.

实现版本控制的your workflow has a multitude of benefits. While not all will be of use to your team, there are a few best practices that will improve the efficiency of your workflow. One of the best version control systems in the industry is GitLab, a powerful tool built by Github. As such, the following tips are from the perspective of that tool for uniformity's sake.

构建您的项目一次。

Build your project and dependencies first and only once if possible. A common practice is to include the build process as one of the early steps in the CI/CD cycle. The idea is to build once per iteration of the CI/CD cycle, minimizing the risk of oversight and uncaught bugs in the project. The result of each CI/CD cycle should be versioned to control the state of the build between pulls.

Commit more frequently, branch less often.

Committing updates frequently supports adding changes in smaller, more manageable chunks which means less opportunity to introduce bugs or issues. This approach allows a team to release updates that are ready to be added with a much lower risk of breaking changes, delays, or downtime. Branching less adds to the clarity and planning for the development and integration updates coming down the DevOps pipeline. Maintaining a clean project tree with minimal branches reduces confusion and code conflict during the development process.

Utilize the power of pull requests.

Pull requests are a fantastic way to track and monitor changes, updates, proposed features, issues, and more. These pull requests get assigned to teams and team members, which helps effectively monitor the lifecycle of your project. Pull requests also offer a lot of flexibility and control over the delegation of tasks and responsibilities. In this vein, your team can communicate and collaborate more effectively, thus fostering a higher quality of work.

2. Incorporate a "Shift Left" approach.

通常，这是在DevOps管道中早些时候开始给定动作的做法。为了DevSecops，它指的是安全实践 - 对于DevOps，它意味着为连续的一切，包括集成和部署而建立。

The Shift Left mentality fosters an improved sense of CI/CD — Continuous Integration and Continuous Deployment. To properly Shift Left, you must include your IT Operations starting early in your DevOps pipeline — after all, a DevOps team cannot function properly without it.

此外，左左心心态不仅与工具有关。左移动左派也包括您团队中的人和实践。

3.利用敏捷方法。

敏捷改善了团队和团队成员的工作流程。从项目开始时实施敏捷方法学则增加了团队的效率。团队效率的提高会带来更好的工作质量和改进的产品。

敏捷方法还增加了发布的速度和频率，并通过将自动化添加到工作流程中进一步支持。自动化任务将简化您的敏捷冲刺并减少团队工作量。

4. Support team-driven workflow.

允许您的团队根据他们对领域的了解来构建工作流程。允许有关哪些工具适合所有人的跨团队反馈。寻找改善沟通和协作的工具有助于平稳工作流程，并通过以前孤立的角色引起的知识差距。

孤立的团队角色之间的鸿沟方面帮助foster a better, cross-team culture. This culture also provides insight into what tools work and which ones don't—adapting to this information is vital for success. Furthermore, Agile sprints will ease the process of responding adaptively to changes in your workflow.

5.建立跨队文化。

Culture is a very different concept from communication and takes more than just clever tools. Building a cross-team culture means improving empathy, compassion, and openness across all teams. Your teams need to know they can safely and comfortably communicate with each other.

A solid, positive cross-team culture has a massive impact on the effectiveness of your teams and the tools they use. This result has a compounding effect on the quality of work provided by your DevOps teams — whether negative or positive is up to you.

6.将自动化添加到您的工作流程中。

在实施自动化时，DevOps团队和工作流程的好处是最好的。但是，在开发管道的早期将自动化整合至关重要。自动化过程之类的过程（例如版本控制，用于跟踪错误和错误，都可以节省大量重复步骤的时间。

将自动化添加到工作流程中还将简化从测试到部署的许多阶段。此外，自动化使您可以专注于需要更个人化的任务。

7.监视和观察项目的状态。

Throughout the lifecycle of your project, it's helpful to monitor the process and track any bugs, errors, and/or issues that may arise.

公开部署项目后，您需要观察任何问题，改进机会或新功能的行为。在任何潜在问题上保持领先地位对于持续不受阻碍的进步和持续改进至关重要。当我们捕捉到漏洞后的错误时，保持连续的工作流程更加困难。捕捉虫子和问题迟到会减慢管道的速度 - 没有人喜欢堵塞的管道。

8. Collect and incorporate feedback.

Collecting and incorporating feedback from users — and even your team — is a vital part of long-term maintenance for your project. It provides insight into the success of your project — as well as its pain points — and thus, outlines your project's roadmap to success. It also serves as valuable metrics for your team that inform future agile sprints and improve your team's workflow.

DevOps Best Practices: Final Thoughts

When it comes to maximizing your team's productivity, implementing these practices is the best place to start. As you may have noticed, these tips carry a lot of overlap, one tactic further bolstering others. When utilized in conjunction, these practices have a compounding — ideally a beneficial — effect.

在项目开头，为这些统一概念纳入最佳实践对于从DevOps工作流中获得最佳状态至关重要。实施行业最佳实践将通过他人的经验来帮助您的团队。从这种情况下，它将节省您数小时的头痛和挫败感，并帮助您的团队建立自我改善的DevOps管道。