Continuous Integration and Continuous Delivery (CI / CD) Pipeline - 1

 In previous post, I mentioned a bit about CI/CD. Now, I will try to explain detailly about CI/CD pipeline that is main skeleton of DevOps approach. Developers and IT operation teams work together to deliver the software during CI/CD pipeline steps. 

The main benefit of CI/Cd pipeline, automation of software releases. Other benefits are reduced deployment time, decreased operaiton costs, continuous feedback ann monitoring so early error detection,  enhanced reliablity and reduced downtime, increased collaboration between teams.

Let's detail of CI / CD pipeline steps a bit more; 


Continuous Integration



  • Plan:  When we are in a process of developing a software in a company, probably this is a part of a project or IT service (change or incident).  Let's suppose Agile project management. (for getting deep information about agile approach, please visit Scrum Website) For project, Scrum Master sets sprint plan. At the end of the sprint, DevOps teams must deliver a "value" (like a working part of  a software)

  • Code: This step includes code creation, modification and application lifecycle management for software asset with version control. DevOps teams could use any of toolset recording to company architecture. (Microsoft Technologies, Open Source Technologies )
Some CI Tools

  • Build: This step is automated build and integration of the entire application. When developer finish the task, merges the code to main branch. Before merge operation, I strongly advice to code review and approval. This will increase code quality and prevent possible errors. In approval step senior developer or team leader could review and approve or back to developer to improve code.

  • Test: After reviewed and built code, unit tests and static code analysis should be run. It will be better if developer write test code. Writing test code will provide automation for unit test process. Othervise, every tests will be run manually by tester. One of the important part of this process is static code analysis. In this step, I prefer to use a static code anayse tool like SonarQube, GitLab etc. After all tests, developer must fix the bugs and vulnerabilities.

I will continue..

Comments

Post a Comment

Popular Posts

Main Topics of DevOps

Image
  DevOps is a methodology that aims to increase communication and collaboration between software development teams, security teams and IT operations teams. Continuous Integration (CI)   : The practice of control mechanism that automate and test all code changes in a code branch. This control provides possible bugs and problems early and fix them immediately. This control cycle provides quality assurance so software quality increases.  Continuous Delivery (CD) : If code has no error and built successfully, it is sent to production environment automatically by creating CD pipeline. This is called continuous delivery. In this concept, we always "use" delivery instead of "deployment" term ☺Continuous delivery provides us transfer any changes of code to test, pre-prod or production environment. We can also automate and monitor this delivery process detailly.  Source Code Version Control Tools : These tools is very useful and important for managing and versioning code ch
Read more

What is DevSecOps?

Image
Dev : Software Development Sec : Information Security Ops : IT Operations. DevSecOps is the collaboration of Software Development, Information Security and IT Operations that includes a set of applications, tools and mindsets.  Main objectives and principles of DevSecOps; Continuous Integration & Continuous Delivery (CI/CD) Automation Logging  Monitoring Collaboration & Comminucation Mindset & Cultural Adaptation DevOps approach covers all part of the software development lifecycle (SDLC) and is involved in all processes from planning to development, testing, deployment, and monitoring of a software. This approach allows software to be developed and delivered faster, more reliably, and more efficiently.
Read more