CI/CD for .NET Core

đź“š Learn more about .NET Core action features, integrations and alternatives.

With Buddy, you can create a pipeline that builds, tests, and deploys .NET Core applications on a push to Git. The configuration is super simple and takes 10 to 15 minutes.

.NET Core pipeline example.NET Core pipeline example

1. Select your Git repository

Buddy supports all popular Git hosting providers, including GitHub, Bitbucket, and GitLab. You can also use your own private Git server or host code directly on Buddy.

Supported Git providersSupported Git providers

2. Add a new delivery pipeline

Enter the pipeline's name, select the trigger mode, and define the branch from which Buddy will fetch your code:

Git repository selectionGit repository selection

Trigger modes:

  • Manually (on click) — recommended for Production
  • On events (automatic) — recommended for Development
  • On schedule (on time interval) — recommended for Staging/Testing
Event-based triggers allow you to run pipelines whenever a push is made to any branch in the repository, or whenever a branch, tag or a pull request is created or deleted. On event pipeline trigger modeOn event pipeline trigger mode

3. Add actions

Buddy lets you choose from dozens of predefined actions. In this example, we'll add 3 actions that will perform the following tasks:

  • Build and test your .Net Core application
  • Upload code to Azure App Service
  • Send notification to Slack

3.1 Build your .NET Core application

Build actions in Buddy are run in isolated containers run from official Docker images. When the pipeline is run, Buddy pulls the container, runs build commands, and uploads the results to the pipeline filesystem.

Look up and click .NET Core on the action list to add it to the pipeline:

Action listAction list

The Run tab lets you determine the commands to execute. The default commands are:

dotnet restore
dotnet build$$

.NET Core action build commands console.NET Core action build commands console

3.1.2 .NET Core version

You can change the version of .NET and install missing packages & tools in the runtime environment tab:

.NET Core action image.NET Core action image

If your tests require a database to run, you can attach it in the Services tab: Services tabServices tab

3.2 Deploy application to Azure

The compiled application needs to be uploaded to the server, Buddy has dedicated deployment actions for IAAS sites like Azure, DigitalOcean, Shopify etc. Look up and click the App Service action to add it to the pipeline:

IAAS action selectionIAAS action selection

When adding the action you can choose where the code should be uploaded:

Azure App Service configurationAzure App Service configuration

3.3 Send notification to Slack

You can configure Buddy to send your team a message after the deployment. In this example we'll use Slack:

Notification actionsNotification actions

If you add this action in the On Failure tab, Buddy will only send the message if something goes wrong with your build or deployment. On failure notificationOn failure notification

4. Summary

Congratulations! You have just automated your entire delivery process. Make a push to the selected branch and watch Buddy fetch, build, and deploy your project. With Continuous Delivery applied, you can now focus on what's really important: developing awesome apps! 🔥

Bear in mind that this article is only a brief example of what Buddy can do. You can create additional pipelines for staging and production environments, integrate with your favorite services (AWS, Google, Azure), trigger tests on pull requests, build Docker images, and push them to the registry—the possibilities are unlimited.
If you want us to create a delivery pipeline for your project, drop a line to support@buddy.works – we'll be happy to help!

Last modified on November 13, 2023

Questions?

Not sure how to configure a pipeline for your process? Reach out on the live-chat or contact support

Get Started

Sign up for free and deploy your project in less than 10 minutes.