Difference between Continuous Integration & Continuous Delivery

What is Continuous Integration and What is not Continuous Delivery ?

Advertisements

Often I have been asked “What is the difference between Continuous Integration and Continuous Delivery”. Thought I will shed some light on this topic.

Martin Fowler has described Continuous Integration as “A development practice that requires developers to integrate code into a shared repository … ”

In addition Thought works also explain Continuous Delivery as “An approach in which teams ensure that every change to the system is releasable, and release any version with the push of a button.”

So what is the difference?

Continuous integration allows multiple developers to integrate the source code into a single code base. This helps the team members to identify integration related issues early and address quickly. CI will lead to minimal SIT cycles.

CI

Once you have implemented Continuous Integration, then you should start working towards Continuous Delivery. Continuous delivery will make sure the changes are ready to deploy to production if required.

CD

Fancy to read more ?

 

Why do I need to learn PowerShell now?

I am well settled and very happy with my day-to-day job, So why do I care about learning PowerShell script ?  This is the thought I had in my mind few years back. However a SQLBits session unleashed the potential of PowerShell. Since then I am learning and using PowerShell a lot. The PowerShell knowledge enable me to automate all activities related to deployment and helped me to achieve the Continuous Integration in the early stages.
So if you are like minded person and asking the same question then read further. I have highlighted the areas where I have seen tremendous benefits of PowerShell.

 
1)    Deployment automation for Microsoft BI
PowerShell will help you to access the functionality of all Microsoft Business Intelligence applications (SSIS, SSAS and SSRS). You can access SQL server to deploy new tables or you can execute a SSIS package.

 

2)    Microsoft’s recommended way for automation
Microsoft has got a good support for PowerShell. It is the standard and recommended automation tool. PowerShell can be used for Windows Server, SharePoint, Office  365, Azure , SSIS, SSAS and SSRS. PowerShell is the first choice to automate the configuration and management activities.

 

3)    PowerShell Automation is a key skill
If you are managing a release for many servers at the same time, then many things could go wrong. Now stay cool with PowerShell script automation. This will reduce manual errors and increase the productivity within the team. It is a key skill for release managers and DevOps consultants.

 

4)    Greater support for DevOps / Continuous Integration tools
Most of the popular tools in DevOps (Chef, Puppet, Jenkins, Bamboo, TeamCity,etc)  does support PowerShell. So you can leverage the PowerShell to support for Build and deployment automation.

 

5)    Easy to learn
If you are familiar with .net framework, then you will be able to learn PowerShell quickly, as the PowerShell has been developed based on .NET.
So, what are you waiting for? Start your PowerShell journey today.

 

Learn PowerShell basics here
https://www.darkoperator.com/powershellbasics/
Bit lazy to read ? You can watch a video to gear up your skill here
https://channel9.msdn.com/Blogs/Taste-of-Premier/PowerShellBasicsPart1
Super excited and want to use PS in your day to day activities?
Deploy your SSIS projects with the help of PowerShell
https://www.simple-talk.com/sql/ssis/deploying-multiple-ssis-projects-via-powershell/
Enable continuous delivery for SSRS
https://www.mssqltips.com/sqlservertip/4481/implement-continuous-delivery-for-sql-server-reporting-service-reports/

Continuous Integration (CI) Tools

ci

After my last blog post, I have got very good response from individuals and organisations for help. Based on their request, I have shortlisted and booked few appointments to help them.

Last week, I had a session with an individual to help him to implement continuous integration for their Data Warehouse. I have discussed about the possible options and recommended few approaches to proceed. I am glad, I was able to share my experience and help them to take the first step.

During the session we have discussed about various CI tools available in the market and thought I will provide a little blog post to help others as well.

Continue reading “Continuous Integration (CI) Tools”