>> Hi everyone. My name is
Angelos and I'm a Program Manager for dot net.
When our code is source-controlled under GitHub.com.
We have the opportunity of using GitHub actions to setup CICD,
continuous integration, continuous deployment.
Let's take a look at how Visual Studio can help us configure
CICD via GitHub actions for
deployments to Azure with just a few clicks.
Here I am in Visual Studio,
I'm going to right-click on my project and select Publish.
I'm going to pick Azure and
Azure App Service Linux as my final published destination.
Here, Visual Studio is helping me
manage all of my Azure resources without leaving the ID.
On the top-right corner, I have my account picker
so even if I'm working with multiple counts,
I can switch between them.
By the way, if you guys have
a Visual Studio subscription that comes with three Azure credits,
so make sure those are activated when you're logged in with it.
If you have multiple Azure subscriptions,
Visual Studio helps you pick the right one to
filter the list by with this drop-down.
You can look at the existing resources,
either grouped by resource group,
because some people like to keep
application dependencies together all in one place.
That's helpful with the default view.
But you can also flip it over to a flat view,
if you're trying to find something alphabetically.
You can search for things if you are almost sure what the name is.
Of course, you can always create
new instances without leaving the ID.
But in this case I'm just going to pick
an existing instance [inaudible].
Now I'm going to click "Next" and check this out.
At this point, Visual Studio knows my project is on
the Git source control and it knows
my remote end point is on GitHub.com.
It's letting me know that I have the option of using CICD
through GitHub actions if that's how I want
to get this application deployed to my destination.
I'm going to go ahead and do just that.
By clicking finish,
what I'm asking Visual Studio to do is go and find
the best GitHub actions workflow template
for myself for this project type.
Visual Studio has done exactly that.
It's telling me that this new workflow has
created is going to be triggered on the next push.
It has even told me not to worry about the publish profile
secret because it has gone ahead to the Azure portal.
It has downloaded the publish profile.
It has put it as a secret in my GitHub repo.
It has wired up this workflow,
which by the way it's written in yaml,
has wired up this yaml workflow
to use up that you have secret doing published.
All I have to do right now is to follow the instructions
and commit this workflow locally and then push it remotely.
I'm going to go ahead and use my Git changes window.
I'm going to commit and push.
This is taking my workflow that Vs has created,
committing into my local repo,
and then it's pushing it to GitHub.com as well.
Because I know that my trigger is on push,
Visual Studio has pushed
the workflow and it has also triggered the workflow to run.
Visual Studio is letting me know the
current status of the workflow,
why it's running and will even let me know when it finishes.
But if I'm really curious and I want to
know exactly what's going on every step of the way,
what I have to do is just follow the link and go check it out.
Here I am in github.com and I'm
looking at this exact deployment as
it happenings every step of the way.
I didn't have to do anything.
I didn't have to customize anything.
All I did was just ask
Visual Studio find one for me and just run it.
The deployment is complete and if I go back to Visual Studio,
it lets me know that's the case as well.
Well, that was fun and pretty simple.
I hope you thought the same as well.
Our journey on GitHub actions tooling is just
starting and would love to get your feedback on it.
Please let us know what you think,
either through social media
or through developer community to visualstudio.com.
Thank you so much. Take care. Bye.