All right.
Time to test out the final test here.
We're going to make sure that we can make a change to all five of the services besides off.
And if we commit those changes, make a PR merge in the PR, we should see all five these additional
services be updated inside of our cluster.
So we're going to essentially go through client expiration orders, payments and tickets, and we're
going to make one small, arbitrary change to each of them.
Let's start off first with client and side of client.
Let's change about on pages.
Index J.S..
About onto each one right here.
Let's just change that to an H to.
So just a small, arbitrary change.
So that's one change down.
Next, I'm going to go to expiration inside of expiration.
I'm going to open up the index.
Yes.
File very similar to the others.
Let's out in a little console log.
At the very top of these start function.
Kate, there's a change to our expiration service.
Then inside of orders, inside the index, not to us file.
Add in another couple of dots to the starting message that we had already added in.
Inside of payments.
Let's open the index out to yes, file, very similar to the others.
Let in a little starting.
Bounce a log at the top.
And then finally inside of tickets.
Open up our index, not to us file.
You guessed it.
Same thing.
A little starting.
OK.
So we now have changes made to five different services.
So we now commit these, create the pull request, merge the request, gets GitHub should detect that
something inside of each of these folders has changed.
And it should run the respective deployment files.
So let's go back over to our terminal.
We're going to change over to our def branch.
We'll see.
All five those changes.
Make sure you've got five changes right here.
We will add all those kimmet them.
And then pushed to our death branch once again.
Then back over on GitHub.
Almost last time we had to do this.
Don't worry.
I know crudities, blurry requests gets kind of tiresome really quickly.
We're going to create a new pull request for the death branch.
Once again.
They'll select Dev and try to merge Dev into master, and I should see the commit that I just made or
really the one commit flushes out changes to client expiration orders, payments and tickets.
They're going to create Despoiler request.
Now, I can run, allow all these tests to run.
I'm just going to hold for a second.
Let these tests run and finish up.
My tests are now complete.
So I'm going to merge the polar request.
All right, so now once again, we can go back up to the top.
Take a look at actions.
Now, we should be able to take a look at our workflows for deploy orders, payments, tickets, expiration
and clients and see that all them have a running job.
Or we can just look at this main display right here as well.
So looks like I'm running a job from client expiration tickets, payments and orders.
Now we can wait for 30 seconds or so once again.
We should see all these jobs go green.
If any of them fail, that means that there's definitely some configuration issue.
And you'll want to take a look at the message.
You can click on the job.
It'll give you some information on why the job failed.
You'll use that as the source to try to debug the thing and figure out what is going on.
Now, if you tried to debug a failing job and you just don't have any idea what's going on and you need
help, I'd be happy to help you.
But you gotta link me to your repository.
I got to see your code to make sure that your repository is public and provide me a link.
You can email it to me or post something in the way and I'll take a look at these failing jobs and hopefully,
Bill, to help you figure out what is going on.
Eventually, all these jobs should go green, which means that hopefully we have successfully built
the images and deployed them off to our communities cluster.
So I'm then going to go back over to my terminal.
We're going to do another get pods and just make sure that we've got some latest versions of all these
images running.
All right.
It looks like I have an ear or two right here.
Sorry.
That pod is still in the process of being deployed.
It looks like everything else is successfully running.
Now, if you have any pods that are persistently airing out, so do give it a minute or two to resolve
and launch all these new pods.
But if after a couple minutes, it looks like everything is still crashing.
I would encourage you to take the name of the pod, let's say the expiration service.
One is crashing and do a QVC T.L. describe pod and then put in the name of the pod.
When you run a command, it will then give you hopefully some reasons on why it is crashing specifically
in the event section down here.
The other thing you can do is pull logs off of a crashing pod.
You can do a QVC T.L. logs and then put the name of the pod in.
There's something like.
Take the name.
But in the name and then you will hopefully see some information right here to help you understand exactly
what is crashing.
All right, so at this point, hopefully, again, after a couple of minutes, you eventually see all
these different prods running successfully.
That means that our application is up and running.
Yay!
That's exactly what we want.
Now, we cannot test this out just yet.
As a reminder, we still do need to get a domain name and register it or assign it to our Ingress Engine
X service.
So we still have a little bit of setup to go through here, but it looks like our cluster is more or
less ready to go.