Skip to main content
DevOps icon showing cogs

This post is from the XebiaLabs blog and has not been updated since the original publish date.

Last Updated Jun 17, 2019 — DevOps Expert

A Manager’s Guide to DevOps as Code, Part 3: Blueprints

DevOps

XebiaLabs’ DevOps as Code approach allows teams to define all of the components of their DevOps pipeline in code that they can version-control, share with other teams, and audit with ease. In Part 1, we took a look at some of the benefits of defining software delivery components as code, and in Part 2, we saw how DevOps as Code works. In Part 3, let’s talk about blueprints.

A blueprint guides teams through a process that automatically generates XL YAML files. The blueprint asks a few questions about the application and the type of environment it requires, and the XebiaLabs command-line interface (CLI) uses the answers to generate YAML files that define configuration items and releases, plus special files that manage sensitive data such as passwords.

After the YAML files are generated, a development team can check them into their source control management system and apply them using the CLI. Applying the YAML files creates configuration items, release templates, and any other components that the team needs.

DevOps as Code

Use XebiaLabs’ blueprints to adopt new technologies

XebiaLabs provides out-of-the-box blueprints that DevOps teams can use to deploy a sample application to a platform such as AWS or Google Cloud Platform. Teams can use XebiaLabs’ blueprints to experiment with the XL YAML format, to get acquainted with XebiaLabs products, and to see what a typical release to a cloud platform looks like.

Create and share your own blueprints

Many enterprises have implemented DevOps as a service by creating a centralized team of experts who set up and run the CI/CD toolchain for application development teams across the organization. These experts can create their own blueprints that enable development teams to start using build, test, provisioning, deployment, and release orchestration tools, even if those teams aren’t familiar with every tool.

For example, teams that are just getting started with static code analysis tools such as Black Duck, Fortify, SonarQube, and Checkmarx can use a blueprint to add those tools to their release pipelines and immediately start benefiting from the automated security and compliance analysis they provide.

Blueprints also allow DevOps teams that have adopted new technologies such as containers and cloud-based infrastructure to spread their expertise across the organization. They can create blueprints for other teams to use as examples or as starting points for migrating their own applications to next-gen platforms.

Try it out with an Amazon EKS blueprint

Learn more

 

More from the Blog

View more
Ascension Launch Banner
Apr 26, 2022

Get ready for peak performance with Digital.ai’s newest AI-Powered DevOps Platform Ascension Release

DevOps
Today, Digital.ai is excited to announce our latest AI-Powered DevOps ...
Read More
Jan 24, 2022

Digital.ai Value Stream Delivery for SAFe®: The key to amazing business outcomes

DevOps
The Scaled Agile Framework (SAFe) is the world’s leading framework for ...
Read More
Dec 09, 2021

How SaaS and cloud-based solutions helped the U.S. Department of Veterans Affairs achieve digital transformation

DevOps
Modernizing legacy systems was an ongoing goal for the U.S. Department ...
Read More
Nov 29, 2021

Increase velocity and reduce risk with AI and machine learning

DevOps
Artificial Intelligence (AI) and machine learning (ML) have proven use ...
Read More
Contact Us