- Tubelator AI
- >
- Videos
- >
- Science & Technology
- >
- Part 7 (Final) - End to End CI/CD Pipeline Testing | CI/CD in Azure Databricks in Tamil
Part 7 (Final) - End to End CI/CD Pipeline Testing | CI/CD in Azure Databricks in Tamil
#databricks #azuredatabricks #azuredataengineer #azureintamil #azuretutorialforbeginners #databricksintamil #cicd #azuredevops #devops
In this Part 7 video of CI/CD in Azure Databricks, I have discussed about how to setup permissions for the PROD environment before deploying the changes in PROD and also the complete end to end CI/CD pipeline testing.
Chapters
TimeStamp:
0:00:00 - Intro
0:02:05 - Setting up permissions in PROD environment
0:04:21 - Complete CI/CD Pipeline Testing
0:10:30 - Outro
Please like, share and subscribe if you like the content and leave your comments below.
For contact,
Email: [email protected]
Instagram: mrk_talkstech_tamil
#AzureDatabricks #ApacheSpark #Sparkcompute #clusters #notebooks #magiccommands #machinelearning #ETL #CICD
Install Tubelator On Chrome
Video Summary & Chapters
No chapters for this video generated yet.
Video Transcript
If you notice, the current CACD setup is like this.
As soon as we merge changes in main branch, the pipeline is running.
First, the dev pipeline is running and we are putting changes in dev workspace.
As soon as we put changes, the prod pipeline is running.
So, the prod pipeline is running immediately after the changes are done.
Most of the companies won't use this method.
Why? Because before the production of the prod pipeline,
only if someone approves the production of the pipeline,
we can get the production environment.
Many companies confuse CICD pipeline
The functionality of the dev pipeline is necessary
As soon as you merge the changes in the main branch
We have to take the latest code and put it in the live location
That is mandatory
But the changes we made in this part
Many companies think that we should deploy it instantly for production environment
There are different reasons for this.
Many people do these changes after the completion of office hours.
That's when the production environment is used.
Many people don't use it.
There are requirements for each company.
The best practice is to get a notification from someone before deploying to the production environment.
By email, we can deploy changes in the dev environment.
we are going to deploy to prod environment
we will get a mail asking if we are approving the changes
the mail will be from higher officials like TL or manager
mostly from the technical person in the operational team
they will decide whether to go to production environment immediately or later
So we can do this check now.
So let's see how we can do it.
So for that I am going to environments.
So in the environments, we are doing this check only for the production environment.
So we don't need dev because we need to have the latest changes in the live folder for the dev.
We have to decide for the production.
So we can use this option to secure the pipeline further
For that I am going to prod environment
Here we have an option called approvals and checks
I am clicking on this
After clicking there is a plus icon here
Add check
I am clicking on this
After clicking there are different kinds of checks
There are many checks
In this there is a check called approvals
So this is what most of the companies use
Basically, I am giving the next option
So here you can add a group or a user
Once you add it
Once the Dev pipeline is run
Before running the prod pipeline
