<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Pravat Kumar Sahoo</title>
    <description>The latest articles on DEV Community by Pravat Kumar Sahoo (@pravatk).</description>
    <link>https://dev.to/pravatk</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F174523%2F2e11348a-faba-4fad-8312-bbf8e1361563.jpeg</url>
      <title>DEV Community: Pravat Kumar Sahoo</title>
      <link>https://dev.to/pravatk</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pravatk"/>
    <language>en</language>
    <item>
      <title>CI/CD of JHipster Spring Boot + React Application using AWS CodePipeline</title>
      <dc:creator>Pravat Kumar Sahoo</dc:creator>
      <pubDate>Sat, 01 Jun 2019 18:33:20 +0000</pubDate>
      <link>https://dev.to/pravatk/ci-cd-of-jhipster-spring-boot-react-application-using-aws-codepipeline-2m5j</link>
      <guid>https://dev.to/pravatk/ci-cd-of-jhipster-spring-boot-react-application-using-aws-codepipeline-2m5j</guid>
      <description>&lt;p&gt;Recently, I worked on creating a CI/CD for a JHipster application. For all the folks out there who are new to JHipster, it's a development tool to generate a Spring Boot + React/Angular/Vue web application (&lt;a href="https://www.jhipster.tech/"&gt;https://www.jhipster.tech/&lt;/a&gt;). The tool also auto-generates a bunch of configuration for different DBs along with CI/CD scripts and Sonar configuration for static analysis.&lt;/p&gt;

&lt;p&gt;Now, if your company has all its infra on AWS, you would like to have the CI/CD also part of the AWS infra for obvious reasons like security! duh!.&lt;br&gt;
In AWS, we have AWS CodePipeline, which may not be as extensible like Jenkins but solves our need as it integrates well with AWS Services. &lt;/p&gt;

&lt;p&gt;Our application needed to have Dev, QA and Prod environment in the same pipeline with multiple stages and approvals which I will go over in a minute or so. Now, I will go through each stage to provide more info.&lt;/p&gt;

&lt;p&gt;Source&lt;br&gt;
The first stage that pulls code from the GitHub repo. You must select the webhook when creating this stage to have the pipeline triggered from GitHub with every merges.&lt;/p&gt;

&lt;p&gt;Build&lt;br&gt;
For building the codebase, I used AWS CodeBuild. The artifact of this stage was the war file from the JHipster application. The war needed to be deployed to an Elastic Beanstalk with tomcat configuration.&lt;br&gt;
The Tomcat configuration for the beanstalk is a bit tricky. One need to ZIP the war and the configuration files for successful deployment.&lt;/p&gt;

&lt;p&gt;Deploy&lt;br&gt;
Once the war is zipped in the build stage, it sits in S3 with Server Side Encryption enabled. This ZIP is then pushed to Elastic Beanstalk for deployment.&lt;/p&gt;

&lt;p&gt;Integration Testing&lt;br&gt;
This stage runs a bunch of Selenium tests configured for the complete Web application. &lt;/p&gt;

&lt;p&gt;QA&lt;br&gt;
Here we have a manual approval step which emails the folks for approval. Once approved, it will deploy to the QA environment.&lt;/p&gt;

&lt;p&gt;One can replicate the same QA stage multiple times for Staging or Production environments as well. &lt;/p&gt;

</description>
      <category>aws</category>
    </item>
  </channel>
</rss>
