HOWTO: Create an ASP.NET CI/CD Application in BuildMaster
  • 13 Apr 2022
  • 3 Minutes to read
  • Dark
  • PDF

HOWTO: Create an ASP.NET CI/CD Application in BuildMaster

  • Dark
  • PDF

Starting in BuildMaster 6.2, application templates are a standard BuildMaster feature designed to simplify the application-creation process without limiting customization.

In this tutorial, you’ll learn how to create an ASP.NET CI/CD application and deploy it using BuildMaster’s CI/CD pipeline. You can also view this tutorial as a video.

For this tutorial you’ll need:

  • BuildMaster
  • BuildMaster extensions installed for
    • GitHub
    • Windows
  • IIS installed on the target machine
  • Know the host name and IIS site name for your ASP.NET application
    • Such as ‘localhost’ and ‘dev.profitcalc.local’

Step 1: Click [Create Application]

In a new instance of BuildMaster, navigate to the Application tab in the top ribbon and click the [Create Application] in the bottom right corner of the window.


Step 2: Select Application Type

The Create New Application page will display a list of application templates available in BuildMaster.

You can always use a Blank Application to start from scratch or Clone Application to begin from an existing application in your installation of BuildMaster.

For this tutorial we'll create an ASP.NET CI/CD application. Click on your preferred application type.


Step 3: Create the Application from a Template

Clicking your desired Application type will open the "Create Application From Template" pop-up window.

Name your application.


Click [Create Application], and BuildMaster will apply the template to your application.


The Application Setup Template displays after the template is applied. The template helps you decide what to configure by providing a description and the link to make changes for each setting.

It also notifies you of settings that must be configured before you can move forward (indicated by a warning symbol).

For, BuildMaster lets you know that you must configure the AppPool name and the Site Host name before continuing. In this tutorial, we’ve set the site host to “localhost” and the AppPool name to “ProfitCalcAppTest,” as the application we’re creating is Inedo’s standard test application, the profit calculator.

Once these values are set, the warning icons will clear, and you can proceed to creating a build via BuildMaster’s CI/CD pipeline.

Step 4: Create a New Build

Now that we’ve created the application, we can build and deploy it with BuildMaster’s CI/CD pipelines.

Navigate to the Builds tab for the application and click [Create New Build].


A pop-up will open and prompt you to "create a release" to begin the build-creation process and enter the pipeline.

Click the [create a release] link in the pop-up to instantly open the "Create New Release" window.

Step 5: Create a Release

In the "Create New Release" window, configure your release to your desired specifications.

You also have the choice to not make any changes.

your title goes here

Read more about Releases on its docs page.


Step 6: Create a Build

Once a Release has been configured, the pop-up will automatically change to the "Create App Build" window.

You can configure the build, or agian not make any changes from the default.


When BuildMaster builds your application, it creates a log as it runs. You can review these logs by clicking on Details on that build stage from the main pipeline.


Running Builds in BuildMaster

Following this tutorial, you will have successfully configured everything. The next pipeline stage will be blue and marked with a refresh symbol to indicate you can deploy to the next stage.

Successes, warnings, and failures in BuildMaster are communicated in three different ways: words, colors, and symbols.

  • A green checkmark means “success”
  • An orange warning sign means a warning and indicates a problem should get your attention but will still let you proceed to the next stage
  • A red encircled exclamation mark means “failure,” and BuildMaster will not let you proceed until the problem is solved or the build is forced through to the next stage


To deploy to Testing, you’ll see a warning and the text ‘force’; this is expected, as Inedo has configured a smoke test into this stage in the pipeline to demonstrate a manual approval.

The default pipeline stages in BuildMaster are Build, Integration, Testing, Production; you can modify these stages to model your organization’s or team’s own pipelines.

You can change the default pipeline via Deploy > Deployment Pipelines > Pipeline Name in that application’s overview page. For example, you can configure the pipeline to automatically promote your build to the next stage after successfully passing the previous stage, add manual approvals, configure deployment windows, etc.

After deploying to Testing, a warning and force will be on the Production stage. Inedo intentionally configured this warning: the profit calculator application was written to include open issues to demonstrate issue tracker integrations with BuildMaster.

Force to Production the Application will be deployed.

You've now successfully created your first application and deployed it via application templates and CI/CD pipelines in BuildMaster.

Was this article helpful?