With these eight kinds of tools, CI / CD is not so difficult
For a long time, continuous integration and continuous delivery (CI / CD) has always been hot, and several people have also released "how to use Docker to achieve PHP command line procedures CI / CD ".
As the saying goes, the work of good things must first of its profits. Today's decimal here to share with you 8 kinds of CI / CD tools, so that your delivery quality and efficiency to a higher level ~
- DockOne Share (108): Based on Jenkins and Kubernetes' CI workflow
- Docker Meetup Hangzhou station, with technology + practice to take you to know this only 4 years old "small whale"
- Container era, this is really what we want the future!
- How to use Docker to build a CI system
- Segment: how to automate our infrastructure to provide productivity?
- Based on Rancher 's Enterprise CICD Environment
Delivery speed is important, but delivery quality is the most important, the following tools, can help the team to improve the quality of the code and compliance.
Ensuring delivery quality while delivering fast and frequent delivery is the toughest problem encountered by the Node.js team.
In fact, keep a quick delivery, the frequent delivery of some secrets is a lot of use of automation. Create an entire automated ecosystem that enables rapid delivery and avoids many problems in a timely manner. The key to developing the automation process is the extensive use of continuous integration and continuous delivery, ie – CI / CD.
This article will use a slightly different approach and share some niche tools that are useful for advancing project lifecycle management at the CI / CD stage.
CodeShip is a simple and elegant CI / CD platform for small and medium scale development teams. Deployment fast, easy to wear, low cost. Ease of use than Travis, and even better is the integration of a considerable number of options, according to their own workflow and development tools to customize the CI / CD workflow.
CodeShip is a good choice if small teams using public clouds (Azure, GCP, or AWS – all have relevant documentation) want to quickly integrate CI / CD workflows into workflows. Of course, you can also consider CircleCI or MagnumCI as an alternative.
Austin's DockerCon conference found a very interesting tool – CodeFresh. In short, it provides pure CI / CD workflow for Docker mirroring.
Although CodeFresh is not a typical CI / CD platform, it provides an interesting application scenario that uses CI / CD on a container to facilitate the development of Docker, Kubernetes and the cloud.
Bamboo is from the Atlassian CI / CD tool, with out-of-the-box features that can be run on hardware. Bamboo is a focused enterprise-class solution that includes highly competitive features, pricing and technical support. Can be deployed in a large-scale production environment.
If the development team used Atlassian related technology and products, then Bamboo is the best choice. She also provides a lot of integration features, slightly modified configuration will be able to achieve the team's ideal workflow.
GitLab platform for CI / CD made some excellent features. After the integration of GitHub, almost all of the CI / CD tools, whether free of charge or open source free of charge are integrated GitLab as the most basic features.
GitLab in a short time to make a series of fine CI / CD features, you can download and use from the official website for free, and built-in Enterprise Edition. So if you use GitLab as a version control tool, you can quickly run the CI / CD system.
Above mentioned Atlassian Bamboo build system, in fact Atlassian BitBucket also integrates CI / CD, called the pipeline (Pipelines). Simply put, the workflow is BitBucket's CI / CD SaaS solution, and if BitBucket is part of the tool integration, then the workflow is the easiest start to try to integrate CI / CD into the workflow.
GitHub's Integration Library
It was only recently found that when you were doing research, GitHub was a collection of systems
Azure developed quickly, it can dock any arbitrary CI / CD platform support. CodeShip and CircleCI are native to Azure's capabilities, and Microsoft provides guidance on the use of the CI / CD and Azure container services based on Jenkins, DC / OS.
Microsoft has done an excellent job of CI / CD, Node.js, and Azure container services to quickly customize the CI / CD deployed under a specific technology stack scenario to achieve seamless application and production.
Heroku also offers an interesting CI / CD tool – Flow. Flow allows you to set the workflow (where the workflow is different from the previously mentioned BitBucket workflow), it can run the test workflow, start the test application, which can be relatively easy to start and rollback, and integrated in GitHub Used to complete the deployment request and deployment status.
Flow is the perfect extension of the Heroku platform. It can start quickly, as Heroku, as always good at that, extend this ability to the CI / CD workflow.
Containers gradually become the core of CI / CD tool chain, 8 kinds of CI / CD tools have been completed, you may wish to try!
Original link: https://dzone.com/articles/8-c … often
Original author: Tierney Cyren