Getting started as a cloud engineer with Gwyneth Peña

Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.
Start free todayGitHub Actions makes it easy to automate all your software workflows. Tim Heuer joins Scott Hanselman to saunter through the process of deploying .NET Core apps to Azure using GitHub Actions.
[0:00:00]- Overview
[0:00:19]- Project setup
[0:04:02]- Configuring the workflow
[0:07:29]- Build job - setting up the environment
[0:13:18]- Build job - configuring the build
[0:16:07]- Getting the publish profile from Azure
[0:17:45]- Build job - handling secrets
[0:20:37]- Build job - deploying to Azure
[0:22:34]- Actions tab in GitHub and workflow log review
[0:24:59]- Adding artifacts to the job
[0:27:59]- Wrap-up
Using GitHub actions for processes outside of GitHub makes no sense to me. GitHub is a source control agent. Why use it as a build agent or a deploy agent or as an Azure interface? My 2 cents is to leave GitHub to do what it knows best, which is source control, code out, code in and merge. Everything else should be handled by the areas that understand those processes best, ie. .net core builds by Microsoft Build, Azure deployments by Azure. But hey, that's just me, make up your own mind.
That's cool, but I'm still missing basic functionality like ingesting and displaying test results. Multi-stage workflows, reuse/templating - any news on that?
Adone123...!!!
1 day ago, foofoodog
For anything much more serious than a hamster blog I think I will stick with Azure Devops Pipelines and Releases with gated stages. At least were I have worked you can't just push to anywhere except maybe dev, and even then that may require some approval checklist or coordination with other team members or other teams. Also not liking yet another yaml file thrown into the mix.
wrote
1 day ago
That's cool, but I'm still missing basic functionality like ingesting and displaying test results. Multi-stage workflows, reuse/templating - any news on that?
Scott you are genius!