Getting Started with BuildMaster: Creating an ASP.NET CI/CD Application
Releasing reliably with BuildMaster is easier than ever before because of application templates. 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 extensions installed for
- 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’
Create an Application with a Template
After you start BuildMaster, you’re going to create your first application. Go to the Applications tab and click Create Application.
The Create New Application page will display the many application templates available in BuildMaster, which are pulled from Inedo’s public ProGet instance. 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.
Select the desired template (in this case, ASP.net) and name your application. Then 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 ASP.net, BuildMaster lets you know that you must configure the AppPool name and the Site Host name before continuing. In this case, 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.
Deploying Applications with BuildMaster
Now that you’ve created your first application, you can build and deploy it with BuildMaster’s CI/CD pipelines.
First, navigate to the Builds tab for your application and click Create New Build.
BuildMaster will prompt you to create a release to begin the build-creation process and enter the pipeline.
Click the create build button to kick off your build. You’ll see that, as 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 screen.
If you have configured everything successfully, 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 will accompany “success”
- An orange warning sign accompanies a warning and indicates a problem should get your attention but that will still let you proceed to the next stage
- A red encircled exclamation mark accompanies “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 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.
NOTE: that 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, and voila! Application deployed!
Congratulations on successfully creating your first application and deploying it via application templates and CI/CD pipelines in BuildMaster.