>> Hi. My name is Abel,
and I'm a cloud developer advocate
specializing in DevOps.
Visual Studio Team Services,
is the best DevOps solution in Azure.
And now, with the general availability
of Azure DevOps Project,
we make it so simple,
to go from nothing at all,
to a full end-to-end DevOps project
in a variety of languages.
And what's in this DevOps project?
You get, a team project in VSTS code
for a sample project in
the language that you picked in the repo.
You also get a CI/CD pipeline
that takes your sample code, builds it,
and deploys it all the way into
the infrastructure it provisions for you up in Azure.
And you get all of this with,
just a couple of clicks.
Now, we all know that containers,
they are the hottest thing in our industry right now,
and DevOps Projects did not forget about containers.
Let's go see how easy it is to go from nothing,
and create a container DevOps Project
for a.Net Node application.
So, the first thing we're going to do is,
we're going to create a new resource in Azure.
And the resource that we want to
create is a DevOps Project.
Now, the first thing is going to ask is
what language we want to use.
Now, for this demo,
we're going to choose a Node.js application.
Now, let's go ahead and click on "Next".
And "Next" is going to ask us,
what framework do we want to use?
Express, sales, or a simple Node.js app.
For this demo, let's go ahead and choose Express.
And now, we'll choose
Web App for Containers click on "Next",
and it's going to ask us,
"What instance of
Visual Studio Team Services do you want to use?"
We can create a brand new one from here,
or we can use an existing one.
I'm going to go ahead and choose my demo account.
So, here's my demo account,
and let's give this project a name,
we'll call this AbelNodeContainer.
And, we need to choose where are we going to deploy this.
Since I live in Seattle,
I'm going to choose the West Coast.
I'll click on "Done",
and that is all I need to do.
Now, I can just kick back,
Azure is going to do his thing,
and build out for me this full end-to-end CI/CD pipeline.
Now, when it's all done building everything for me,
I get a portal, and the portal look something like this.
We're on the left hand side,
I have deep links into the full CI/CD pipeline,
and on the right hand side,
I have links into
all the resources that it created for me in Azure.
Now, these links, these are deep links.
So, if I click on this master link,
it's going to take me directly into the code repository
in the Visual Studio Team Services Project
that it created for me.
So, as you can see,
this is just my sample code for my Node.js Application.
Now, lets go ahead and jump into the builds so you
can see what type of build we created for you.
Now, what we did is we created a build pipeline,
that makes sense for the technology that you picked.
So, what we did is, we created
a build that makes sense for a
Node.js application that's going
to be turned into a Docker image.
So, we build the image,
and then we push that image
into Azure Container Registry.
And when we're done doing that,
we will go ahead and we'll release it.
And I'll show you the release pipeline that we have.
Now the release pipeline that we create, once again,
is going to be a release pipeline that makes
sense for the technology that you picked.
So, we create one dev environment, and when we deploy,
since we're deploying this container
into Azure App Service,
we can do that very simply with
one deployed Azure App Service Tasks.
So, once it deploys,
it deploys it as a container into Azure App Service,
we can click on the application endpoint,
and there is our app
running in a container in Azure App Service.
Now, there's nothing more for you to do.
Everything just works, everything is perfect.
However, if you wanted to go in and
customize your code or your build in release pipelines,
you still have full control,
where you can go in and do whatever you need to.
So, if you jump into VSTS,
remember your code, this is just a get-repo.
So, there's nothing stopping you for
cloning this repo onto your hard drive, and then,
you can just go ahead,
change the code however you need to,
"Upload" this back into the repo and then,
it will kick off the build and release.
If you wanted to configure your build and
release pipelines, not a problem.
Remember, the build in VSTS,
it's nothing more than just a test
runner that does one task,
after another, after another.
So, if you wanted to customize this build,
all you need to do is just add or
remove tasks in the order that you need it.
And out of the box there are
hundreds of tasks that you can choose from.
If what you want to do doesn't exist out of the box,
that's not a problem.
Go ahead and check out the marketplace,
where in the marketplace,
our partners have created over 500 build and release
tasks that you can just drag
onto the screen and start using.
So, as you can see,
very simple to customize
your build and release pipeline if you need to.
However, out the box, everything just works.
Azure DevOps Projects, they make creating
your end-to-end DevOps pipelines
into Azure incredibly simple.
With a couple of clicks,
everything just starts working,
and yet you still have
full control over your CI/Cd the pipelines,
to customize and configure it to do what ever you need.
And now, with the GA of Azure DevOps Project,
we support containers into Azure as well.
If you need more information about Azure DevOps Project,
go to docs.microsoft.com. Thank you.