In 2019, DevOps still remains something of a codeword: a sphere reserved to developers trained in writing complicated scripts for tools only they know how to use. Tools whose purpose is to make your life easier with automation, but somehow:

在2019年，DevOps仍然是一个代码字：保留给开发人员的领域，这些培训人员只有在知道如何使用工具的情况下才能编写复杂的脚本。 旨在通过自动化使您的生活更轻松的工具，但在某种程度上：

• take weeks to configure and launch

  需要数周的时间来配置和启动

• require a designated developer to oversee

  需要指定的开发商来监督

• cannot be easily modified

  不能轻易修改

Buddy is a CI/CD tool that doesn't require DevOps experience and can be used by beginner and expert developers alike. We did that by replacing scripts with preconfigured actions(builds, tests, deployments, etc.), and packing the whole thing in a clear and telling GUI. And making it run deadly fast.

Buddy是一种CI / CD工具，不需要DevOps经验，可以供初学者和专家开发人员使用。 为此，我们用预配置的操作（构建，测试，部署等）替换了脚本，然后将整个内容打包在一个清晰易懂的GUI中。 并使其快速运行。

Remember the times when setting up remote servers was a chore? Now you can spin a droplet on DigitalOcean in 55 seconds with 1-click. This is what Buddy does to DevOps: frees automation from the constraint of configuration scripts, documentation, and sluggish performance.

还记得设置远程服务器的时间吗？ 现在，您只需单击一下鼠标，即可在55秒内在DigitalOcean上旋转液滴。 这是Buddy对DevOps所做的事情：使自动化摆脱了配置脚本，文档和性能缓慢的约束。

用例 ( Use Case )

One of our clients is Bay Area News Group, the largest publisher of newspapers in San Francisco. "We are using Buddy to automate Continuous Delivery tasks for three main repository branches: QA, Staging, and Production," says Phillip Marashian, the developer behind Bay Area's delivery process.

我们的客户之一是旧金山最大的报纸出版商湾区新闻集团。 湾区交付流程背后的开发商Phillip Marashian表示：“我们正在使用Buddy自动化三个主要仓库分支的连续交付任务：质量保证，分段和生产。”

The main repo is hosted on GitLab and has 2 submodules which need to be updated before the deployment. The workflow looks like this:

主仓库位于GitLab上，有2个子模块，需要在部署前进行更新。 工作流程如下所示：

• fetch changes from GitLab

  从GitLab获取更改

• update sub repositories

  更新子存储库

• build application

  建立应用

• upload files to DO droplet

  将文件上传到DO Drop

And here's how it looks reproduced into Buddy:

这是复制到Buddy中的样子：

"All this was possible before Buddy, but the config files would have been extremely complicated and testing would have been very slow," says Philip. "I've done extensive CD with yaml files and manual scripts. It's all doable, but it's very abstract and hard to test."

Philip说：“在Buddy之前，所有这些都是可能的，但是配置文件将非常复杂，并且测试将非常缓慢。” “我已经用yaml文件和手动脚本制作了广泛的CD。这都是可行的，但是它非常抽象并且很难测试。”

The green icons in the pipeline are Node actions which prepare the environment with npm install and pull the files from external repositories. Buddy uses isolated Docker containers in which you can run your own commands:

管道中的绿色图标是Node操作，它们使用npm install准备环境并从外部存储库中提取文件。 Buddy使用隔离的Docker容器，您可以在其中运行自己的命令：

"[Before] I had experienced issues building production files. The build script required significant resources over and above what I needed to server my app. I would have ended up paying a lot for a cloud server just so I could build the files. With Buddy it was trivial to trigger the build script."

“ [之前]在构建生产文件时遇到了问题。构建脚本需要大量资源，而不是服务器应用程序所需的资源。我本来要为云服务器支付很多钱才可以构建文件。伙计，触发构建脚本很简单。”

与DigitalOcean集成 ( Integration with DigitalOcean )

Finally, the application is built and deployed to a DigitalOcean droplet. Authentication details, deployment paths, trigger conditions—all can be easily set from the GUI:

最后，将应用程序构建并部署到DigitalOcean Droplet 。 身份验证详细信息，部署路径，触发条件-均可从GUI轻松设置：

Deployments are the crown feature of Buddy. This is what makes them stand out from other CI/CD tools:

部署是Buddy的主要特征。 这就是使它们在其他CI / CD工具中脱颖而出的原因：

• only changed files are deployed (no need to deploy the whole repository every time)

  仅部署更改的文件（无需每次都部署整个存储库）

• the deployment mechanism is heavily optimized for high speed

  部署机制已针对高速进行了优化

• user passwords and server credentials can be stored in ENV VARs

  用户密码和服务器凭据可以存储在ENV VAR中

• you can roll back changes with one click

  您可以一键回滚更改

"With the DO action I was able to upload the files and didn't have to worry about authentication tokens, server paths, etc.," says Phillip. We also asked him why he went for DO instead of other providers. He delivered an answer which perfectly aligns with Buddy's take on DevOps:

Phillip说：“通过DO动作，我能够上传文件，而不必担心身份验证令牌，服务器路径等问题。” 我们还问他为什么他去DO而不是其他提供者。 他给出的答案与Buddy对DevOps的看法完全吻合：

"They have a very slick UI. Of all cloud providers I’ve used their UI makes it easiest to get a server box up and running with no headache. I can do what I want within their platform without having to figure out how to do it. [Also], they make it very easy to point a domain to a server if you’re using them for domain DNS."

“他们的UI非常漂亮。在所有云提供商中，我使用他们的UI可以最轻松地启动服务器并轻松运行。我可以在他们的平台上做我想做的事，而不必弄清楚该怎么做。 [此外]，如果您将域用于域DNS，它们使将域指向服务器变得非常容易。”

YAML ( YAML )

Although the GUI is what makes Buddy stand out, Buddy fully supports YAML configuration as well, making it easier to switch from other CI/CD tools. For example, here are the two last actions, an SSH script and a Slack notification, defined in the YAML config:

尽管GUI使Buddy脱颖而出，但Buddy也完全支持YAML配置，从而更容易从其他CI / CD工具切换。 例如，以下是最后两个操作，即在YAML配置中定义的SSH脚本和Slack通知：

So if you're one of those guys who even check the weather from the terminal and are afraid of more than 4 colors displayed at once, you can breathe a sigh of relief.

因此，如果您是什至从终端查看天气的人之一，并且害怕一次显示超过4种颜色，那么您可以松一口气。

摘要 ( Summary )

We are very excited about the future of Buddy. The feedback we are getting from developers is outstanding: 90% of the 10000+ paid accounts come from organic traffic (i.e. word-of-mouth recommendations), which is absolute madness. Reaching out to DigitalOcean users is a great way to spread the word about CI/CD, and

我们对Buddy的未来感到非常兴奋。 我们从开发人员那里得到的反馈非常出色：10000多个付费帐户中有90％来自自然流量（即口碑推荐），这绝对是疯狂的。 接触DigitalOcean用户是传播关于CI / CD的好方法，并且

Buddy is the perfect vessel to do it, especially that both platforms are blazing fast and have a very similar user-friendly approach to UX.

Buddy是执行此操作的理想工具，特别是两个平台都在快速发展并且对UX具有非常相似的用户友好方法。

Right now, we are genuinely interested in how DigitalOcean will develop its Kubernetes services and how we can help developers better streamline K8s management on DO's clusters. One thing is for sure: the future is here, and we are super happy to be a part of it.

目前，我们对DigitalOcean如何开发其Kubernetes服务以及我们如何帮助开发人员更好地简化DO集群上的K8s管理非常感兴趣。 可以肯定的是：未来就在这里，我们很高兴能融入其中。

翻译自: https://scotch.io/tutorials/how-buddy-turns-devops-to-noops-the-digitalocean-way