Welcome to the project, the name of this project is continuous delivery hybrid.
The reason why we are calling a hybrid is because we are going to use Jenkins' as a continuous integration
and A.W. Fast and sassed services.
To follow along in this project, you should have done continuous delivery project with Jenkins and
Tool and continuous delivery project with eight of us, so we're going to use existing resource of our
previous two projects.
And also all the knowledge that you have gathered in this previous two projects.
So in this project, we're going to use Jenkins' for continuous integration and we're going to use eatables
some part and Sassella says, like we're going to use code word Bienstock ideas and a few other services,
Jenkins' will be running on easy to instanced or you can be running it anywhere else.
The situation will be more apt when you have a hybrid environment that where you are running your candidates
integration or some work load on computers and operating systems and also leveraging a W.S. or any cloud
computing managed services.
And that is the reason why we are calling it a continuous delivery hybrid.
OK, let's see the success that they're going to use in this project.
We're going to use.
Get for version control system, GitHub, jenkins' for continuous integration.
Eatables, goodwill for running software testing.
SoundCloud for the SoundCloud dashboard, so you don't need to have a sonic a server running, you're
going to use SoundCloud to push all our core analysis result and displayed and also quality gates on
that.
Our application will be hosting on Bienstock.
And we are going to use our ideas for the database if you want.
You can even include active Amcu and elastic cash in this project that's optional.
But if you want, you can integrate that as well.
And we'll understand how.
OK, so let's achieve our goals.
But before that, we'll see the architecture of continuous delivery pipeline in this project.
OK, so once we're done setting up our project, our architecture will be like this developer makes
a coaching and push the changes to get how?
Jenkins is going to detect any change, fetch the change run could test locally unit test.
If this passes, it goes to the next level where we are going to do good analysis, we're going to use
Czech style sonar scanner and when generate the report, the report will be pushed to Sonor Cloud,
not the Sonic Observer, the sonic cloud, which will also have quality gates based on the result.
If it's a success, then we build the artifact.
And all the dependencies will be downloaded from the Internet.
They're not going to use Nexxus all here, but once the packaging of the artifact is done, it will
be uploaded to a three bucket and from there it will be deployed to Bienstock environment by using Bienstock
plugin was the deployment is completed on a staging environment.
Then we are going to run software testing by using a code built service which will validate our deployment.
If it's a success, it can be promoted to the next level and another Bienstock plugin setting that is
going to deploy artifact to production being environment.
And Bienstock will be also connected to ideas.
And if you want, you can integrate also elastic cache and active MQ with this, as we have seen in
our previous projects.
So it seemed continuous delivery, what but we are mixing we are mixing jenkins' continuous integration
power with enablers, cloud services.
Let's see how we are going to do it.
Let's see the flow of execution now.
All right, first, we need to already have a continuous integration setup.
So if you have been cadenas delivery project or continuous integration project in Jenkins', you should
already have the set up.
And we need only Jenkins server, we don't need Sonor CubeSat or Nexus server for this, once we have
the set up already running and testing, then will start setting up our applications tag by using Bienstock
and ideas so folks will create audio security group will launch Bienstock Environment.
And we're also going to set up Ibbs.
Then initialize our ideas database and also security group update so Bienstock can.
Connect to our earliest instance.
If you want, you can launch elastic cash and active MQ over here is optional.
Then we will go to SoundCloud, we're going to generate a token over there.
We're going to do so, a cloud integration with Jenkins server.
So in the project continues, delivery on A.W. as we have integrated SoundCloud with could build something
here, SoundCloud integration with Jenkins'.
So when we get we're going to put this on the clock token that we have got and one more extra property,
Sonador organization and Souness Canada job.
Once we did all this, our SoundCloud scanning job, we are going to make some changes, so it it it
uploads the result to SoundCloud.
And will distort.
Then we'll go to go back to Amazon console.
We're going to create an IBM user, this user.
Is will be used by Jenkins to access eatables, cloud services, Caudwell ancestry.
So we need to give to policies to this user goodwill policy and industry Buchardt policy.
So by now, we should have a Bienstock environment ready and we'll have you all to access that environment,
we're going to store that information to barometer's to.
Systems manager barometer's tool, so goodwill can fetch that water from their.
Then we're going to set up a job in Jenkins' to deploy our de facto Bienstock staging environment,
next will create a software testing job.
And in this job, you're going to call it a place called Bill Job, which was running software testing.
The same job will call, but we have to make some changes in those jobs first.
Of course, we need a plugin plug in with IBM authentication.
And in the job, we're going to make some changes.
And those changes need to be also done on code, Bill.
So we'll go to Established Code Bill Service.
We'll switch to this branch CD hyphen, Eatables Hyphen Jenkins'.
From the previous setup, we used Selenium Otoscope Branch in this project, we are going to use this
Branch CWD hyphen, Eatables Syphoned Jenkins'.
We're going to update our bill.
There will be changes.
One obvious change is going to take the usual being sexual from the prime minister and few other changes
we have.
Once we have all these jobs, we are going to connect all of them together in Jenkins' Pipeline and
then we'll it.
If you want, you can create one more job which can do deployment to production, Bienstock environment,
that's optional.
If you want, you can integrate that job as well.
For this, you will need one more set up of Bienstock and ideas, but it will be same job as deployed
to Bienstock job staging to be similar job.
Except the world will be different Bienstock environment name that will be different.
OK, now let's make this happen.
Let's go to AWB management console.