1 00:00:00,310 --> 00:00:01,970 ‫So next we have CodePipeline. 2 00:00:01,970 --> 00:00:03,130 ‫So how do we know that 3 00:00:03,130 --> 00:00:05,640 ‫CodeCommit and CodeBuild are connected? 4 00:00:05,640 --> 00:00:07,710 ‫Well, we can connect them using CodePipeline. 5 00:00:07,710 --> 00:00:09,220 ‫So CodePipeline is going to be a way 6 00:00:09,220 --> 00:00:12,040 ‫for us to orchestrate the different steps 7 00:00:12,040 --> 00:00:14,800 ‫to have the code automatically pushed to production? 8 00:00:14,800 --> 00:00:15,700 ‫What does that mean? 9 00:00:15,700 --> 00:00:19,110 ‫Well, maybe we want to define a pipeline that takes the code 10 00:00:19,110 --> 00:00:21,660 ‫builds it, tests it, provision some servers 11 00:00:21,660 --> 00:00:24,120 ‫and then deploys the application on those servers 12 00:00:24,120 --> 00:00:25,630 ‫but it could be more complicated. 13 00:00:25,630 --> 00:00:27,720 ‫And so to orchestrate all these steps 14 00:00:27,720 --> 00:00:28,810 ‫you need a pipeline tool 15 00:00:28,810 --> 00:00:31,170 ‫and this is going to be CodePipeline. 16 00:00:31,170 --> 00:00:32,690 ‫And so you may or may not 17 00:00:32,690 --> 00:00:34,810 ‫have heard of the term CICG, which may stand 18 00:00:34,810 --> 00:00:37,430 ‫for Continuous Integration and Continuous Delivery. 19 00:00:37,430 --> 00:00:38,830 ‫It is the whole concept 20 00:00:38,830 --> 00:00:41,470 ‫that every time a developer pushes the code 21 00:00:41,470 --> 00:00:44,540 ‫into a repository, it is being built, tested 22 00:00:44,540 --> 00:00:46,950 ‫and deployed on to some servers. 23 00:00:46,950 --> 00:00:49,731 ‫So if we look at CodePipeline, say we have code 24 00:00:49,731 --> 00:00:51,630 ‫as an orchestration layer, 25 00:00:51,630 --> 00:00:53,500 ‫it will take its code from CodeCommit 26 00:00:53,500 --> 00:00:56,180 ‫build it with CodeBuild, then decide to deploy it 27 00:00:56,180 --> 00:00:58,810 ‫with CodeDeploy, and may be deployed 28 00:00:58,810 --> 00:01:01,990 ‫into an Elastic Beanstalk environment as one example. 29 00:01:01,990 --> 00:01:03,750 ‫But it's just one way of building a pipeline, 30 00:01:03,750 --> 00:01:05,360 ‫okay, there's so many different ways. 31 00:01:05,360 --> 00:01:06,530 ‫So why would you use CodePipeline? 32 00:01:06,530 --> 00:01:08,530 ‫Well, the benefits is that it's fully managed. 33 00:01:08,530 --> 00:01:10,730 ‫It's compatible with so many services such 34 00:01:10,730 --> 00:01:12,350 ‫as CodeCommit, CodeBuild 35 00:01:12,350 --> 00:01:15,660 ‫CodeDeploy, Elastic Beanstalk, CloudFormation, GitHub 36 00:01:15,660 --> 00:01:19,120 ‫and other third party services and custom plugins. 37 00:01:19,120 --> 00:01:22,560 ‫And it gives you fast delivery and rapid updates. 38 00:01:22,560 --> 00:01:27,140 ‫So it is at the core of the CICD services within AWS. 39 00:01:27,140 --> 00:01:30,410 ‫And so anytime you see orchestration of pipeline 40 00:01:30,410 --> 00:01:33,710 ‫in your exam, you have to think AWS CodePipeline. 41 00:01:33,710 --> 00:01:35,190 ‫So that's it, I hope you liked it. 42 00:01:35,190 --> 00:01:37,140 ‫And I will see you in the next lecture.