Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.

Start free today

Learn how to deploy .NET Core apps to Azure with GitHub Actions

Play Learn how to deploy .NET Core apps to Azure with GitHub Actions

The Discussion

  • User profile image
    Vgrhbbfdbbv

    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.

  • User profile image
    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.
  • User profile image
    mmisztal

    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?

  • User profile image
    yogeshk04
    Thank you for sharing :)
  • User profile image
    Cuongle1985

    Adone123...!!!

  • User profile image
    TimHeuer
    @Vgrhbbfdbbv:Hi! GitHub Actions is built upon foundations that also power Azure Pipelines. The great part is that the actions themselves do the work, so the Azure team publishes the actions that deploy to Azure. For projects already on GitHub, using Actions is a natural step to keep the code and process in the same place. You are right though, this is a tool, and anyone can choose whatever tools that work best for them!
  • User profile image
    TimHeuer

    1 day ago, foofoodog
    wrote

    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.

    Totally understand about the approval flow aspects of Pipelines. I love those as well. I hope that Actions will implement those soon! Pipelines provides a good UI on building up the YAML file for you but also in the end is just a YAML definition as well. Each provide a great benefit to those who choose either.
  • User profile image
    TimHeuer

    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?


    Agreed those are valuable! I don't know updates on plans for those in Actions or timeframes.
  • User profile image
    Mark​Orlassino
    Great stuff! I liked the show format! Thank you!
  • User profile image
    Gofightnguy​en
    This was great. I would enjoy an episode on using GitHub Actions to create/maintain your Azure infrastructure, such as creating the App Service using something like Terraform
  • User profile image
    PRASHANT

    Scott you are genius!

  • User profile image
    Simoncverac​ity
    Really really liked this episode - great content (i.e. i've used github actions "at speed" before but never broken down the steps) so thanks. Also the longer format was great for this content. I like the chilled slow vibes of this longer episode. I'd recommend (my humble opinion only) you try a longer episode again! Thanks both!

Add Your 2 Cents