Skip to main content

Understanding Continuous Integration[CI] and Continuous Delivery[CD]

What is Continuous Integration(CI) ?
Continuous Integration is a development practice that requires developers to integrate code to a shared repository several times a day.
All developers are writing functions and developing new feature, service, etc. on their individual workstation and then they will commit and send the Pull Request(PR’s) to the mainstream. This happens on a regular basis and as there’s no time frame when the changes are being merge into the master repository, its painful, every single time manual build is cumbersome and time consuming process. A version control system is being monitored. When a commit is detected, a build will be triggered automatically. If anything failed during the process, the system will notify and send alert to the admin and the respective developer of the feature. With continuous CI process, you could be able to detect problems, bugs, dependency issues, in the earlier phase of development life cycle.
Each Integration is verified by an automated build to detect integration errors as quickly as possible. This approach leads to significantly reduced integration problems and allow the team to build the robust software more rapidly. The steps for achieving CI server process is shown in the below diagram. Note that there are many other ways to achieved CI into your system. This is one which I felt best and good for beginners to easily understand.
Continuous Integration Server
Automate the process of building, testing and reporting:
  1. All Developers working on their own feature branch check-in and sends a Pull Request(PR) to the upstream several times a day.
  2. Version Control System(VCS) receives all the PR’s by the individual developer and merge it once it’s verified by the maintainer. It also indicates the CI server so it will start the process of Build server.
  3. Build server starts building your project after the integration of above merge and check if everything works as expected which includes continuous testing process.
  4. The above build reports the status of the build along with detail results. You can check the logs of build process and confirm if it meets the desired state.
  5. Each integration should have feedback. The feedback will be provided based on the result in the above step.
  6. Notify the admin and respective developers of the project regarding the feedback so that they will take appropriate action to resolve it.
What is Continuous Delivery(CD) ?
Continuous Delivery(CD) is a software engineering approach in which teams keep producing valuable software in a short cycle and ensure that the software can be reliably released at any time.
The vary environment, system dependencies cause a problem and new bugs arise while building the system which became difficult to maintain. Some problems we face into the process as, maintaining different environments, package versions, repositories, rollbacks, etc.
Developers used to throw their code over the metaphorical wall, and operators were responsible for keeping that code running in production. Developers were concerned with shipping code, while operators were concerned with reliability. This misalignment is filled by the continuous DevOps process.
Continuous Delivery Phases (Reference Link)
As shown in the above diagram, Continuous Delivery process consist of the our SDLC phases with automation at each phase. With this we can deliver the changes to your customers quickly in a reliable way and achieve continuous end-to-end automation i.e. one click deployment, quick release, etc. So, no specific schedule is needed to deploy new things. And, you could easily manage, debug and deploy micro-services. Your code must be robust, which should cover all the edge test cases which will make the standardized system workflow. This solves the complex problems at deploying stage and make the process seamless. You can release more often, thus accelerating the feedback loop with your customers.
The continuous delivery automates the entire software delivery process. Every commit will trigger the automated build, test and deploy to the respective environments. The deployment to production can be manual to validate the desired state while pushing to production. It focuses on reducing the application lifecycle while delivering values faster with best strategy to production with-in a quick succession.

Comments

Post a Comment

Popular posts from this blog

How to use Ngx-Charts in Angular ?

Charts helps us to visualize large amount of data in an easy to understand and interactive way. This helps businesses to grow more by taking important decisions from the data. For example, e-commerce can have charts or reports for product sales, with various categories like product type, year, etc. In angular, we have various charting libraries to create charts.  Ngx-charts  is one of them. Check out the list of  best angular chart libraries .  In this article, we will see data visualization with ngx-charts and how to use ngx-charts in angular application ? We will see, How to install ngx-charts in angular ? Create a vertical bar chart Create a pie chart, advanced pie chart and pie chart grid Introduction ngx-charts  is an open-source and declarative charting framework for angular2+. It is maintained by  Swimlane . It is using Angular to render and animate the SVG elements with all of its binding and speed goodness and uses d3 for the excellent math functio...
Post a Comment
Read more

Understand Angular’s forRoot and forChild

  forRoot   /   forChild   is a pattern for singleton services that most of us know from routing. Routing is actually the main use case for it and as it is not commonly used outside of it, I wouldn’t be surprised if most Angular developers haven’t given it a second thought. However, as the official Angular documentation puts it: “Understanding how  forRoot()  works to make sure a service is a singleton will inform your development at a deeper level.” So let’s go. Providers & Injectors Angular comes with a dependency injection (DI) mechanism. When a component depends on a service, you don’t manually create an instance of the service. You  inject  the service and the dependency injection system takes care of providing an instance. import { Component, OnInit } from '@angular/core'; import { TestService } from 'src/app/services/test.service'; @Component({ selector: 'app-test', templateUrl: './test.component.html', styleUrls: ['./test.compon...
Post a Comment
Read more

How to solve Puppeteer TimeoutError: Navigation timeout of 30000 ms exceeded

During the automation of multiple tasks on my job and personal projects, i decided to move on  Puppeteer  instead of the old school PhantomJS. One of the most usual problems with pages that contain a lot of content, because of the ads, images etc. is the load time, an exception is thrown (specifically the TimeoutError) after a page takes more than 30000ms (30 seconds) to load totally. To solve this problem, you will have 2 options, either to increase this timeout in the configuration or remove it at all. Personally, i prefer to remove the limit as i know that the pages that i work with will end up loading someday. In this article, i'll explain you briefly 2 ways to bypass this limitation. A. Globally on the tab The option that i prefer, as i browse multiple pages in the same tab, is to remove the timeout limit on the tab that i use to browse. For example, to remove the limit you should add: await page . setDefaultNavigationTimeout ( 0 ) ;  COPY SNIPPET The setDefaultNav...
Post a Comment
Read more