There are quite a few build and deploy options available to developers these days. Previously, I have wrote about using a combination of Team City and Octopus Deploy. These are still good tools, but will likely require a bit of setup and probably require a VM.
A more recent trend is to have your actions linked to your repository, where you can have it all self contained and in one place. There are pros and cons to both, but I'm gonna show you how you might do that with GitHub Actions.
I work mostly with .NET, so lets take a look at the workflow for that. With .NET Core you can now use Linux (and macOS) as your build target. Here we're using
We're also setting the relevant
DOTNET_VERSION and running our commands,
dotnet build and
dotnet publish. Problems with the build will be visible within GitHub and you can follow along with the progress.
Finally, we're pushing our published version of the app to Azure Web Apps using a publish profile. You could also choose to generate a NuGet package and push to a feed for distribution.
Note, you can also build .NET Framework apps, that will look a little different but the concept is the same. You'll target
windows-latest as that is a prerequisite for .NET Framework, and the commands will be
If you've got a FE repo, then you'll likely want to use npm to compile some assets and package them up. Here's how you can do that.
We've set up our
NODE_VERSION and then run the commands,
npm install and
npm build. At that point, we might want to package up the assets or deploy as an application.
There are lots of other options available to you, without going into all of them here, I encourage you to take a look through the docs and see what you might want for your needs.
If you're interested in what's installed on the runners, then take a look at this repo which contains the full list of software and spec for each.
The approach here can also be used for similar tools such as Bitbucket Pipelines or Azure Pipelines. Choose what fits the bill for you.