Instructor - In this section,
we finally get to deploy our application
after a ton of work.
So we've made all of our changes to our K eight folder
all the config files in there.
We've got our Deploy SH file set up
and the Travis dot YAML file set up.
So to initiate our deployment
all we have to do is commit our work
and then push it to our master branch on GitHub.
Travis CI is then going to automatically pick
up our changes, run this Travis dot YAML file, and then
hopefully eventually run the deploy dot SH file as well.
Now, before we do anything here
I want you to know that this entire setup process
even though I took really good notes
on my side of things, and I've gone
through this process many times entirely possible
that I made a mistake, entirely possible
you made a mistake or a typo someway along the line.
So if it looks like at any stage you get an air message
first thing to do is to go
to the next section along with me.
Maybe I got the same air message as well
and so we'll do a little bit of troubleshooting together.
If that still doesn't help, then you can always go
over to the QA and I'll do my best to help you
understand exactly what went wrong.
All right, so let's get to it.
I'm gonna first begin by going back over
to my terminal inside the complex directory.
I'll do a get status inside of here and we'll verify that,
yep, we've got a couple of different files changed.
I'm going to add both those changes, and then
I'll commit both of them and say added deployment scripts.
And then I'm going to do, I get Push Origin master.
All right, here's the moment of truth.
So we'll run that command, it's gonna push our changes up
and then we're going to flip over to our browser.
We'll open up a new tab and go to Travis CI dot org.
And then once here, we'll go
to our new multi K eights project.
Now, I want you to be aware
that the first thing that can possibly go wrong is
you might not see the build show up inside of here.
If you do not see the build show up inside of here
then it very likely means
that there is a typo somewhere inside
of your Travis dot YAML file.
If anything is wrong inside the Travis dot YAML file
you're never gonna see the build show up here,
and Travis is going to essentially just silently fail
and it's going to never pick up any change
and it's not gonna give you any air message.
Now you notice that my bell just got picked up.
So if you wait a couple minutes and you still don't
see anything show up here, then it very likely means
that you have a typo inside this file.
So if you have a typo inside of here
remember the entire source code for this entire course is
in a Git repository, and it's linked towards the very start
of the course.
So you can always pull open.
As a matter of fact, I got a link for it right here.
Let's give it to you right away.
Make life easy.
So the link to the repository with all the completed code
is my Docker or my GitHub ID, Steven Greer slash docker CAS
and so inside of here, you can find that complex directory
and it's not in here yet because I haven't updated
this repo yet.
But inside of the complex directory, you're going
to see my dot Travis dot YAML file.
So you can always compare yours against mine.
Now if you do compare,
do remember that you cannot just do a
direct copy paste because there is some
project specific information in here like the project ID,
the compute zone, the cluster name
and then some other differences inside of here like
the Docker ID and some details around the open SSL command.
But you can at least compare and contrast to
make sure you don't have any obvious typos.
All right, so we'll take a pause right here.
It looks like I've already got a nice little air going on
so we're gonna take a quick break.
We're gonna figure out what just went wrong and
we'll start fixing it.
So quick pause and I'll see you in just a minute.