On January 15, 2018, the Alibaba Cloud developer application product CodePipeline (commercialized) was officially released. It is a SAAS-based product that provides continuous integration/continuous delivery capabilities and is fully compatible with Jenkins' capabilities and usage habits. By using Alibaba Cloud CodePipeline, you can easily implement continuous integration and delivery from code to application in the cloud, so that you can quickly iterate and evolve your product functions.
Product features and advantages
1. Integration with multiple source code management platforms: It can seamlessly integrate with GitHub, Bitbucket, Alibaba Cloud Code and other platforms to obtain source code.
2. Code compilation & unit testing: Currently, it provides compilation & UT capabilities for Java, Nodejs, PHP, Python, Python2/3, and Go development languages.
3. Deploy to ECS environment: Provide a channel through the open source Slat protocol to deploy code, compile and build products to ECS or VM environment; and support the use of Packer to create ECS image scenarios.
4. Provide a containerized integration solution: it can independently support Docker image compilation, and at the same time support compilation and security check through Alibaba Cloud Container Image Service, and connect with Alibaba Cloud Container Service, which can be automatically published to the Kubernetes cluster of Container Service through CodePipeline , currently supports multiple publishing methods such as blue-green/grayscale publishing.
5. DevOps Practices: Ability to improve the speed and quality of software updates by automating the build, test, and release process by running a consistent set of quality checks. Let our philosophy education have a product basis.
Product Architecture
The system architecture and business relationship of the CodePipeline product are shown in the figure below. The tasks you configure and execute are roughly divided into two categories: compiling/testing tasks and deployment tasks. PipelineService is like a scheduler and will deliver your tasks to different Task clusters work.
· Compilation/testing tasks are performed through the sandbox runtime environment resource pool. The data of each task execution is in the container environment, the environment does not store data, and the results of the task (such as the compilation and construction products) will be uploaded to the container environment. Managed in your OSS.
· Deployment tasks currently support ECS-type environments and container-type environments, and will also issue instructions to your operating environment through the Deploy Service to pull deployment products stored on your OSS for release.
Scene assembly introduction:
As shown in the diagram below, a containerized continuous delivery solution. After the developer submits the code to the source code management platform, the continuous integration service will pull the code for construction, which can be done through the compiling service for docker build, or through the container image service. After the build, the Docker image can be tested, and the test passes Then deploy it by using the plugin of the container service.
In this process, CodePipeline acts as CI and CD Service, and your running environment can also be ECS environment, VM, etc.