- Docs Home
- Getting started
- XL Release
- Overview
- Installation
- Get started with XL Release
- Manage your installation
- Model your releases
- Release your software
- Release overview
- Create and start releases
- Configure release properties
- Schedule releases
- Start a release from an archived release
- Start a release from a template
- Start a release from another release
- Create a release from a Git repository
- Add a phase to a release or template
- Add a task to a phase in a release or template
- Import a release template
- Trigger releases
- Work with running releases
- Work with plugins
- Using reports
- Customize XL Release
- API and scripting overview
- Create custom task types
- Create custom configuration types
- Create custom trigger types
- Extend the XL Release GUI
- Declare custom REST endpoints
- Create custom tiles
- Create custom task types
- Create custom configuration types
- Using scheduling in scripts to connect to long running jobs
- Implement a custom failure handler
- Listen to XL Release events
- Configuration settings
- Release manuals
- XL Deploy
- Overview
- Installation
- Get started with XL Deploy
- Manage your installation
- Logging
- Start XL Deploy
- Shut down XL Deploy
- Back up XL Deploy
- Upgrade XL Deploy
- The XL Deploy repository
- Configure the repository
- Configure XL Deploy to fetch artifacts from a Maven repository
- Manage security
- Manage system settings
- XL Deploy configuration files
- Configure failover for XL Deploy
- High availability with master-worker setup
- Add, start, and use workers
- Configure active/hot-standby mode
- Configure the task execution engine
- Troubleshoot the Jackrabbit JCR repository
- Configure XL Deploy client settings
- Enable XL Deploy maintenance mode
- Update the XL Deploy digital certificate
- The XL Deploy work directory
- Reclaim disk space on an XL Deploy server
- Hide internal XL Deploy server errors
- Automatically purge packages according to a user-defined policy
- Automatically purge the task archive according to a user-defined policy
- Specify file encoding on the XL Deploy server
- Automatically archive tasks according to a user-defined policy
- Best practices for maintaining XebiaLabs tools
- Connect to your infrastructure
- Set up applications and environments
- Prepare your application for XL Deploy
- Create a deployment package
- Define application dependencies
- Configure an environment
- Using placeholders and dictionaries
- Working with deployment packages
- Preparing your application for XL Deploy
- Understanding deployables and deployeds
- XL Deploy manifest format
- Deprecated XL Deploy manifest format
- Using the XL Deploy Manifest Editor
- Understanding archives and folders in XL Deploy
- Add an externally stored artifact to a package
- Extend the external artifact storage feature
- Add a package to XL Deploy
- Export a deployment package
- XL Deploy for developers
- Tips and tricks for deployment packages
- Deploy an application
- Deployment overview
- Understanding the XL Deploy planning phase
- Steps and step lists in XL Deploy
- Understanding tasks in XL Deploy
- Deploy an application
- Use tags to configure deployments
- Preview the deployment plan
- Use orchestration
- Working with deployments
- Stopping, aborting, or canceling a deployment
- Schedule a deployment
- Update a deployed application
- Staging artifacts in XL Deploy
- Monitor and reassign deployment tasks
- Make previously deployed property values available in a PowerShell script
- Undeploy an application or deprovision an environment
- Perform canary deployments
- Perform dark launch deployments
- Perform hot deployments
- Deploying an externally stored artifact using the XL Deploy CLI
- Schedule or reschedule a task
- Using the deployment pipeline view
- Deploy to remote datacenters
- Get started with provisioning
- Introduction to the release dashboard
- Work with the CLI
- Work with plugins
- Create an XL Deploy plugin
- Base plugins and the deployed object
- Implement custom XL Deploy plugpoints
- Add a checkpoint to a custom plugin
- Step options for the Generic, PowerShell, and Python plugins
- Sample Java-based XL Deploy plugin
- XL Deploy plugin tutorial
- Standard plugins
- Middleware plugins
- Apache Tomcat
- BizTalk
- F5 BIG-IP
- GlassFish
- IBM WebSphere Application Server
- IBM WebSphere Process Server
- IBM WebSphere Liberty Profile Server
- IBM WebSphere MQ
- JBoss Application Server 5 and 6
- JBoss Application Server 7 and up
- Microsoft Internet Information Services
- Microsoft Windows
- NetScaler
- Oracle Service Bus
- Oracle Service-Oriented Architecture
- Oracle WebLogic Application Server
- Provisioning plugins
- Container platform plugins
- Tools
- Community plugins
- Using control tasks
- Using the explorer
- Using XL Deploy reports
- Customize XL Deploy
- Release manuals
- DevOps as Code
- Get started with DevOps as Code
- Install the XL CLI
- XL CLI command reference
- Work with the YAML format
- YAML snippets reference
- Manage values in DevOps as Code
- Track progress using XL CLI output
- Manage risk profiles
- Manage XL Deploy permissions in YAML
- Manage XL Release permissions in YAML
- Manage XL Release folder permissions in YAML
- Tutorial: Managing an XL Release template as code
- Blueprints
- API and CI references
- Plugins
- XL Release plugins
- XL Deploy plugins
- Standard plugins
- Middleware plugins
- Apache Tomcat
- BizTalk
- F5 BIG-IP
- GlassFish
- IBM WebSphere Application Server
- IBM WebSphere Process Server
- IBM WebSphere Liberty Profile Server
- IBM WebSphere MQ
- JBoss Application Server 5 and 6
- JBoss Application Server 7 and up
- Microsoft Internet Information Services
- Microsoft Windows
- NetScaler
- Oracle Service Bus
- Oracle Service-Oriented Architecture
- Oracle WebLogic Application Server
- Provisioning plugins
- Container platform plugins
- Tools
- Community plugins
- Videos
- Community
- Fix Trackers
- Archive
Valid since:
XL Release 6.0.0
Migrating templates to folders
XL Release 6.0.0 introduced folders, which allow you to organize related templates and releases. This topic describes how you can migrate existing templates from earlier versions of XL Release into folders. It shows an example in which all templates related to releasing the XL Release product will be moved to a folder called XL Release.
Step 1 Create the folder
First, create the folder. Go to Design > Folders to get an overview of the current folders.
Click New folder and create a top-level folder called XL Release. You need the Create top level folders global permission to do this; if the New folder button is disabled when no folder is selected, ensure that your global role has the permission.
Click the folder to open it. You will see that it is empty.
Step 2 Set up folder permissions
Go to the Permission tab to set up access to the folder.
When you create a folder, XL Release gives it three default teams and puts you in each team as the only member. You can think of a “team” as a local role that only applies to the folder and to the releases and templates that are in it. Note that all templates and releases in a folder will have the security settings that are defined on the folder.
The default teams are:
- Folder owner: For XL Release admins who require access to administrative tasks on the folder
- Template owner: For template designers
- Release Admin: For the release managers
At this point, you should define who has access to what. For example, assume that you have the following global roles:
- Power users manage the XL Release server instance
- Team Toad develops the XL Release product and manages the release process
- Technical writers write the documentation and release notes
- Users everybody in the organization
An easy configuration would be:
This is enough to get started. The teams will be expanded as templates are moved into the folder.
Step 3 Move the templates
To view a list of all templates, go to Design > Templates. It contains templates that are stored in a folder and templates that have not been moved to a folder yet. Use the filter box to find the templates you are interested in.
Templates that are already in a folder will have the folder name under their title; for example, the “Configure XL Release” template is in the “Samples & Tutorials” folder. Find the template that you want to move and click Move. XL Deploy will ask you for the destination folder.
After selecting the folder, you can choose how to handle the permissions.
Select Add teams and permissions…. This will copy the teams that were defined on the template to the folder, adding any new teams and merging team members from the template into the teams that are already defined on the folder. This option helps you to populate the teams on the folder.
If you choose Remove teams and permissions…, the teams on the template will be discarded and the teams on the folder will not be changed. Use this option if you have already set up teams on the folder and don’t want them to change.
Step 4 Verify the results
Go to the folder by clicking its name under the template in the template overview. Go to the Teams & Permissions tab and you will see which teams were added.
As you can see, several teams have been added and the permissions are updated accordingly.
Step 5 Continue to move templates
Now continue to move templates with the Add teams and permissions… option. When you are done, review the teams and permissions on the folder again. It will give you a consolidated view of all teams. This will apply to all templates in the folder.
For example, assume that “Bob Mediano” (shown in the screenshots above) has left the company. You can remove him from the “Dev” team and the change will apply to all templates. (Don’t forget to click Save.) It is also good practice to review that all permissions are assigned to the appropriate teams. Make any permission changes that are needed, and you will be ready for future future releases that will be started from templates in the folder.
Working with nested folders
In XL Release, you can nest folders. For example, you can set up a structure with a parent folder named Products that contains XL Deploy and XL Release subfolders.
It is important to realize that by default, folders inherit permissions from the parent folder. So in this case, the XL Release folder takes its permissions from the Products folder.
In this case, when you move a template into the XL Release folder and you choose the Add teams and permissions… option, the teams and permissions are actually added to the Products folder.
If you don’t want this to happen, clear the Inherit teams and permissions.. option on the Teams & Permissions tab of the subfolder to which you are moving the templates. When this option is disabled, all teams and permissions are defined directly on the folder. Changes to the teams and permissions of the parent folder do not apply to the subfolder, so you have to decide what works best for you.