CI/CD for .NET Core
đź“š Learn more about .NET Core action features, integrations and alternatives.
Buddy lets you create delivery pipelines that will build, test and deploy your .NET Core application on a single push to the branch. The pipelines consist of actions that you can configure depending on your needs.
.NET Core pipeline example
Configuration is very easy and takes only a couple of minutes.
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 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 selection
Branch assignment — this is the branch from which Buddy will deploy. If you set the trigger mode to On push, Buddy will execute the pipeline upon every push to that branch.
Trigger modes:
- Manual (on click) — recommended for Production
- On push (automatic) — recommended for Development
- Recurrently (on time interval) — recommended for Staging/Testing
3. Add actions
Buddy lets you choose from dozens of predefined actions. In this example, we'll add 4 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
Look up and click the .NET Core action to configure it. Here you can choose the .Net Core version and determine the commands to execute. The default commands are:
dotnet restore dotnet build$$
.NET Core action build commands console
If your tests require a database to run, you can attach it in the Services tab:
Services 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. Head to the Deploy to IAAS section and select your upload action (Azure in our case):
IAAS action selection
When adding the action you can choose where the code should be uploaded:
Azure 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 actions
If you add this action to Actions run on failure Buddy will only send a message if something went wrong with your build or deployment.
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 July 13, 2022