index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Scribbles by Rifhan</title>
    <link>https://blog.rifhanakram.com/</link>
    <description>Scribbles by Rifhan</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Oct 2020 00:29:58 +0530</lastBuildDate>
    
    <atom:link href="https://blog.rifhanakram.com/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>CI/CD for Monorepo&#39;s With Jenkins</title>
      <link>https://blog.rifhanakram.com/posts/jenkins-pipeline-monorepo/</link>
      <pubDate>Tue, 27 Oct 2020 00:29:58 +0530</pubDate>
      
      <guid>https://blog.rifhanakram.com/posts/jenkins-pipeline-monorepo/</guid>
      <description>&lt;p&gt;Monorepo is an approach in managing source code under a product, team or company within a single repo as oppose to multi-repo where a single product/application is contained within its own git repository.&lt;/p&gt;
&lt;p&gt;The two approaches has its own pro&amp;rsquo;s and con&amp;rsquo;s. In this article i will not be discussing on what is the best approach as it entirely matters on the context we work, rather i will walk the through the challenges of Automated CI/CD with &lt;strong&gt;mono-repo&lt;/strong&gt; and how we can over come them with structure and some magic with &lt;a href=&#34;https://www.jenkins.io/doc/book/pipeline/&#34;&gt;Jenkins Pipeline&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;challenges&#34;&gt;Challenges&lt;/h2&gt;
&lt;p&gt;Due to the nature of multiple applications residing in a single repo it is not trivial to setup a CI/CD job that detects changes and executes only the &lt;strong&gt;impacted applications related CI/CD pipeline&lt;/strong&gt;. Some of the steps that contain in a typical pipeline are,&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Building the code&lt;/li&gt;
&lt;li&gt;Running automated tests&lt;/li&gt;
&lt;li&gt;Creating and versioning a deployable artifact&lt;/li&gt;
&lt;li&gt;Deploying that artifact&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Lets look at how we can tackle this problem with Jenkins.&lt;/p&gt;
&lt;h2 id=&#34;some-jenkins-magic&#34;&gt;Some Jenkins Magic&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;sample structure in a mono-repo setup with jenkins pipeline&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;pre&gt;&lt;code&gt;.
├── src                                 
    ├── react-app
        ├── Jenkinsfile     
    ├── node-app
        ├── Jenkinsfile                                                               
└── Jenkinsfile                 # main jenkinsfile
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;If we consider a structure like above, with jenkins we could setup the main Jenkinsfile in the root of the repository as a &lt;a href=&#34;https://www.jenkins.io/doc/tutorials/build-a-multibranch-pipeline-project/&#34;&gt;multi-branch jenkins job&lt;/a&gt;. This job can be connected with your remote repository such that it triggers via a webhook when a PR is merged to your mainline branch. You can get creative with the triggers depending on the workflow your team follows.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;A stage inside the main Jenkinsfile is shown below&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;pre&gt;&lt;code&gt;stage(&#39;Execute Jobs&#39;) {
    failFast false
    parallel {
        stage(&#39;react-app ci&#39;) {
            when {
                changeset &amp;quot;src/react-app/**&amp;quot;
            }
            steps {
                build job: &amp;quot;react-app-job&amp;quot;, parameters: [string(name: &#39;branch_name&#39;, value: env.BRANCH_NAME)]
            }
        }
        stage(&#39;node-app ci&#39;) {
            when {
                changeset &amp;quot;src/node-app/**&amp;quot;
            }
            steps {
                build job: &amp;quot;node-app-job&amp;quot;, parameters: [string(name: &#39;branch_name&#39;, value: env.BRANCH_NAME)]
            }
        }
    }
}

&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;In the above example the &lt;strong&gt;changeset&lt;/strong&gt; condition walks through the git changelog for that particular change and checks if there is any change within the given path. If a change is detected then the &lt;strong&gt;build job&lt;/strong&gt; step executes the related jenkins job.&lt;/p&gt;
&lt;p&gt;Note - &lt;em&gt;&lt;strong&gt;failFast&lt;/strong&gt; is set to false to avoid failure of the entire pipeline if one job fails.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Once we have this setup we can go about and setup separate pipeline jobs for each application in the repository.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Below is an example on how the main multi-branch job will look in Jenkins&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;img src=&#34;https://blog.rifhanakram.com/img/jenkins-multi-main.png&#34; alt=&#34;jenkins-multi-main.png&#34;&gt;
In the above image the multi-branch job has executed when a change has been pushed to the master branch. When we navigate into the master branch execution we can see the pipeline as shown below,&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://blog.rifhanakram.com/img/jenkins-multi-stage-view.png&#34; alt=&#34;jenkins-multi-stage-view.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;In the stage view we can see that build #9 contains changes only for 1 application and build #10 contains changes for both.&lt;/p&gt;
&lt;p&gt;This is an awesome and quick setup with Jenkins for a monorepo. I&amp;rsquo;m a big fan of Jenkins due to its flexibility and extensibility specially with declarative &lt;a href=&#34;https://www.jenkins.io/doc/book/pipeline/&#34;&gt;Jenkins Pipeline&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Tech Talks</title>
      <link>https://blog.rifhanakram.com/posts/tech-talks/</link>
      <pubDate>Tue, 27 Oct 2020 00:29:58 +0530</pubDate>
      
      <guid>https://blog.rifhanakram.com/posts/tech-talks/</guid>
      <description>&lt;h2 id=&#34;grpc-microservice-communication-with-aws-app-mesh&#34;&gt;gRPC Microservice Communication With AWS App Mesh&lt;/h2&gt;
&lt;p&gt;This talk was done at the 2020 July AWS User Group Colombo meetup. In this talk i walk through the challenges of microservice communication with gRPC and how we can use AWS App mesh to manage this communication and overcome the challenges mentioned.&lt;/p&gt;
&lt;h3 id=&#34;references&#34;&gt;References&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.youtube.com/watch?v=qXeBwMVCnSw&#34;&gt;Video&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://speakerdeck.com/rifhanakram/grpc-microservice-communication-with-aws-appmesh&#34;&gt;Slides&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://github.com/rifhanakram/gRPC-appmesh-demo&#34;&gt;Code Samples&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
  </channel>
</rss>