Sample CI/CD pipeline using AWS CodePipeline

Recently, I created a sample AWS CI/CD pipeline with a demo ReactJS application. It automates the basic phases of continuous integration and delivery/deployment.

I have used below AWS services

  • Pipeline services: CodePipeline, CodeBuild, CodeDeploy

  • Compute platform: Elastic Compute Cloud or EC2

  • Storage service: S3

  • Event/Log/Alert: CloudWatch

  • Notification: SNS

For code repository, I have used GitHub. Though I explored AWS’s CodeCommit (AWSs own private version control service) and it has a lot of features, hence it can be used but based on your requirement.

#aws #amazon #ci/cd pipeline #aws codepipeline #devops

What is GEEK

Buddha Community

Sample CI/CD pipeline using AWS CodePipeline
Matt  Towne

Matt Towne

1589791867

Serverless CI/CD on the AWS Cloud

CI/CD pipelines have long played a major role in speeding up the development and deployment of cloud-native apps. Cloud services like AWS lend themselves to more agile deployment through the services they offer as well as approaches such as Infrastructure as Code. There is no shortage of tools to help you manage your CI/CD pipeline as well.

While the majority of development teams have streamlined their pipelines to take full advantage of cloud-native features, there is still so much that can be done to refine CI/CD even further. The entire pipeline can now be built as code and managed either via Git as a single source of truth or by using visual tools to help guide the process.

The entire process can be fully automated. Even better, it can be made serverless, which allows the CI/CD pipeline to operate with immense efficiency. Git branches can even be utilized as a base for multiple pipelines. Thanks to the three tools from Amazon; AWS CodeCommit, AWS CodeBuild, and AWS CodeDeploy, serverless CI/CD on the AWS cloud is now easy to set up.

#aws #aws codebuild #aws codecommit #aws codedeploy #cd #cd pipeline #ci #ci/cd processes #ci/cd workflow #serverless

Sample CI/CD pipeline using AWS CodePipeline

Recently, I created a sample AWS CI/CD pipeline with a demo ReactJS application. It automates the basic phases of continuous integration and delivery/deployment.

I have used below AWS services

  • Pipeline services: CodePipeline, CodeBuild, CodeDeploy

  • Compute platform: Elastic Compute Cloud or EC2

  • Storage service: S3

  • Event/Log/Alert: CloudWatch

  • Notification: SNS

For code repository, I have used GitHub. Though I explored AWS’s CodeCommit (AWSs own private version control service) and it has a lot of features, hence it can be used but based on your requirement.

#aws #amazon #ci/cd pipeline #aws codepipeline #devops

Rory  West

Rory West

1621691340

Creating CI/CD Pipeline for AWS ECS

Amazon Elastic Container Service (ECS) is Amazon’s solution for running and orchestrating Docker containers. It provides an interface for defining and deploying Docker containers to run on clusters of EC2 instances.

In this blog post I will explain how to run simple node.js application in Amazon EC2 Container Service (ECS) and then in the next part we will create CI/CD Pipeline.

You can download the source code from my GitHub account.

Prerequisites

  1. You should have VPC created in your account with Public and Private Subnets and Private subnets should have a route to NAT Gateway.
  2. Amazon Elastic Container Service (ECS) Cluster
  3. Application Load Balancer
  4. ECR Repository
  5. Permission to Create IAM roles, policies
  6. AWS CLI
  7. Application Load Balancer

#docker #aws #devops #aws-ecs #ci/cd pipeline

Rory  West

Rory West

1621868100

Creating CI/CD Pipeline for AWS ECS

In Part-1 of this tutorial I have explained how you can run sample node js applications in AWS ECS. In this tutorial I will explain how to Create CI/CD Pipeline using AWS Code-Pipeline.

You can download the source code from my GitHub account.

Prerequisites

  1. Code Commit Repository
  2. You should have VPC created in your account with Public and Private Subnets and Private subnets should have a route to NAT Gateway.
  3. AWS ECS Cluster with Service Running Task Definition (Refer: Part — I)
  4. AWS ECR Repository
  5. Permission to Create IAM roles, policies

Architecture Diagram

#aws-ecs #automation #devops #aws #ci/cd pipeline

CI/CD Tutorial for Xamarin Android with Google Play Publishing in Azure DevOps | Part 2.

If you haven’t seen part 1, click here, and start build up your CI/CD pipeline now.

Part 2 Contains:

  • Configuring build with creating signed APK, and making artifacts from it
  • Setting up branch policy to master

Configure some magic

Let’s go back to Pipelines. Edit your previously created pipeline by clicking the three dot on the pipelines row.

Edit the previously created pipeline

CI is based on cloud machines hosted somewhere over the world. This computers called as agents. They are used to follow your instructions, defined in the yml file. The base Xamarin.Android yml is only to build your code. But we will make some additional steps in order to create a signed APK of every build. Follow up, to complete this setup.

Recommended branching strategy for this is to keep a development branch, and pull request your feature branches to it, and finally pull request the development branch to the master, and keep your master is always at your production version. The figure below shows visually this method. Source: https://dzone.com/articles/feature-branching-using-feature-flags-1

Create a signed APK or bundle from every build

First, set up some variables for this pipeline. You will find a Variables button on the right top of the tab. Click on it.

#xamarin #azure #azure devops #ci #ci/cd #pipeline #pipelines #xamarin