Getting Started with Application Templates in BuildMaster

Slow time-to-market (TTM) is unsustainable in 2020.​ The most successful companies get applications out of developers’ hands and into the hands of their customers as fast as possible without ever compromising security and compliance.

Increasing TTM often requires new tools and long onboarding. But not with BuildMaster’s re-imagined application templates! These true, script-level templates give you fast time-to-value, allowing even minimally trained junior developers to release enterprise-quality, compliant applications within three minutes every time.

In this tutorial, you’ll learn how to use BuildMaster’s application templates and how to create your own templates in BuildMaster.

See the simplicity and power of these templates in action—watch the webinar.

Using the Application Templates in BuildMaster 6.2 

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.  

To create your own application from scratch or with a tool for which Inedo doesn’t yet offer a template, select “Blank Application,” and “Clone Application” allows you to clone (and then edit) an existing application. 

However, 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 the purposes of this tutorial, we’ll use GitHub CI/CD.

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

After naming your application, click “Create Application,” and BuildMaster will run a function that applies the template to your application. 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 company, 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 functionality adds extra layers of compliance and security into your instance of BuildMaster. This functionality makes it easy to maintain compliance standards like SOX, which bar developers from releasing their own work directly into production. BuildMaster’s pipelines are highly customizable, so a compliance officer can set up a customized template, adding different gates and approvals into your pipeline as needed to meet your security and compliance standards, and then save that template for future use by your developers. 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, which you can download here. ProGet Free gives you the necessary functionality to save custom templates to BuildMaster, but your organization may require the extra security and compliance features offered by ProGet Basic or Enterprise.  

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!).