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 May 03, 2012 — DevOps Expert

XL Deploy Cookbook: Adding a check to the Deployment Checklist


This Cookbook entry describes how to add a single check to the Deployment Checklist in the Release Dashboard. We will take an existing pipeline that has Dev, Test, Acceptance and Production environments. We will show how to add a single condition 'Signed off by Release Manager' that will be put on the Production environment.

Adding the check to synthetic.xml

First, we will have to tell XL Deploy that the new condition exists. We do this by adding properties to existing XL Deploy types. Deployment conditions in XL Deploy are defined by pairs of properties, one on the Environment and one on a DeploymentPackage (a version of an application). To introduce the property into the XL Deploy's type system, we have to edit the synthetic.xml file on the XL Deploy Server. The synthetic.xml file can be located in $DEPLOYIT_HOME/conf. For more information about the XL Deploy type system, please refer to the Reference Manual and the Customization ManualFirst we add the property to the Environment type. Locate the definition of udm.Environment and add the property:
<type-modification type="udm.Environment">
  <property name="requiresSignedOffByReleaseManager" kind="boolean"
    required="false" category="Deployment Checklist" />
This means that for any Environment there will be an additional boolean property. The property has to start with the prefix requires in order to be picked up by the Release Dashboard. The next thing we have to do in the synthetic.xml is to tell XL Deploy that deployment packages will have a property that can satisfy the check specified above. Note that each version of an Application will have different sets of properties checked during its voyage through the deployment pipeline. We therefore set the property on the udm.Version type. Locate the type udm.Version and add the property. The property name is based on the property set on the Environment, but with the requires prefix replaced by satisfies.
<type-modification type="udm.Version">
  <property name="satisfiesSignedOffByReleaseManager" kind="boolean"
    required="false" category="Deployment Checklist"
    label="Signed off by Release Manager" />
What we just did: for each individual deployment package we add the possibility to satisfy the constraints imposed by the requires property of the Environment. After saving the file, restart the XL Deploy Server for the changes to take effect.

Configuring the Environment

Now that we have added the check, we can enable it for an environment. In this case, we will enable it only for the Production Environment, but of course you could enable it for any environment. Once a check has been enabled on an environment, only deployment packages that satisfy the requirements can be deployed to this environment. Deployments that do not satisfy the check are not allowed. We can easily configure the Environment from the UI. After restarting the XL Deploy Server, reload the UI in the browser. Got to the Repository tab, and find the Production Environment in the Environments tree. Double-click on it to open its editor and click on the "Deployment Checklist" tab. The new property will not be enabled, meaning that this check is not active for the Production Environment. Tick the box to enable it and save.Now go to the Release Dashboard and you will see that the condition has been added

Setting permissions

Here's a summary of the relevant security settings for the Release Dashboard:
  • The repo#edit permission on the DeploymentPackage is used to check if a user is allowed to set or unset checks in the Deployment Checklist.
  • When viewing the deployment pipeline, only the environments are shown if the user has readpermission on it. For example, if user 'developer' has access to the Development and Testing environments, she will only see those environments in the Release Dashboard and not the others.
  • Regular deployment permissions (deploy#initialdeploy#upgrade) apply when a deployment is initiated from the Release Dashboard.

More from the Blog

View more
Ascension Launch Banner
Apr 26, 2022

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

Today, is excited to announce our latest AI-Powered DevOps ...
Read More
Jan 24, 2022 Value Stream Delivery for SAFe®: The key to amazing business outcomes

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

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

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