Getting Started with BuildMaster: Using Application Templates

BuildMaster 6.2’s application templates will get you up-and-running with CI/CD in minutes. This tutorial will run you through

  1. Creating a new application in BuildMaster using a built-in Template
  2. Creating your own application templates to help you automate even faster

Creating a New Application Template

In your instance of BuildMaster, navigate to “Applications” and select “Create Application.” 

This will take you to the “Create New Application” page. Here you will see Standard Applications, Featured Templates, and (at first unpopulated) User Templates.  

You can create an application from scratch with “Blank Application”, or use “Clone Application” to copy everything in an existing application, but Templates are designed to get you up-and-running even faster.

The list of “Featured Templates” is growing every day (and soon will feature a community support function). If creating an application for which an existing template exists, select that template to begin.

For this tutorial, we’ll use the “GitHub CI/CD” template.

After selecting your template (in our case, GitHub), give your application a name. While these will be versioned as you move along the process. Choose one with meaningful names, understandable to other people on your team. We’ll use “Profit Calc” here. 

After naming your application, click “Create Application,” and BuildMaster will create the application based on the selected template. After success, the application setup template displays. 

This table features links and descriptions for the different parts of the application you can alter to meet the needs of your organization, team, and this particular application.  

For example, selecting “GitHub Repository” (top left) allows you to add the resource credentials necessary to point your application to a GitHub repository.  

Note: The GitHub ProfitCalc application is Inedo’s sample application. The secure resource defaults to “Use in application: ProfitCalc,” “Organization name: inedo,” and “Repository: ProfitCalc.” You can change all these elements as needed for your application.

And that’s it! It is THAT easy to create applications in BuildMaster!  

If you need to return to the setup template, from the application’s page, hover over “Settings” and select “Application Setup.” 

Creating Your OWN Templates 

Remember that unpopulated “User Templates” section? BuildMaster makes it easy to set up
and save your own, organization- or team-specific templates.  

This will not only save you a lot of time in creating your own application, but it allows you to consistently enforce compliance and security standards across new applications.

For example, if your organization is regulated under SOX, and developers are barred from releasing their own work directly into production, you can create SOX-compliant templates that can be approved by compliance officers. BuildMaster’s pipelines are highly customizable, and a custom template will ensure pipelines created have specific gates, manual approvals, and so on.  

This allows developers to do as much as compliance allows in your pipelines, blocks them from acting when necessary, and gives end-to-end visibility, even when direct
action isn’t possible. 

Note: This step requires ProGet Free (or a paid edition), which you can download here.

After you have customized your template to your particular needs, you’ll see a prompt asking if you want to “Review Changes.” Click this. 

BuildMaster then shows you the changes you’ve made, highlighting successful changes in green, changes with a warning in yellow-orange, and changes that will cause a break in red. The callout at the top reads “There are unsaved changes to the Release pipeline” with options to “Continue Editing” or “Commit Changes” for successes or warnings. This messaging changes if there are breaks, making it easy to catch problems before they can cause trouble. 

Once you commit these changes to BuildMaster, go to “Settings” and select “Advanced Settings.” 

Under “Advanced Settings,” select “Export as Application Template…” at the bottom. This is where your instance of ProGet comes into the picture. 

BuildMaster will then prompt you to title the template, and you can optionally enter a description and even select a custom icon to display in the “User Templates” section in BuildMaster. 

Over in ProGet, check to see that your template has exported. In this case, we named our new template “Inedo Console App,” so we will search “Inedo.” 

And voila! There it is! 

Clicking the application displays details and lets you view the various versions of the template. 

And when you pop back into BuildMaster and go to create a new application, you’ll find your customized application template under the “User Templates.” 

It really is that easy! Test the templates yourself; download BuildMaster 6.2 today: 

Download BuildMaster

(Check out the install guide for more information.) 

Already have an earlier version of BuildMaster? Visit the “Administration” page in your instance to access the upgrade checklist before switching to 6.2 (it’s a big change, so we want to make sure it goes smoothly!).