- 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 8.0
Using release groups
In XL Release 8.0 and later, the release group feature is available. By grouping releases together, you can manage a collection of releases as one group. Releases can be added to multiple release groups, and into multiple folders. The release group feature also provides estimates on when the release group will start and finish, based on the schedule and other tasks that are being executing at the same time.
Release group overview screen
This screen shows all release groups based on status. From this screen, you can view start and end dates, completion status, duration, and the number of releases per group. You can also edit group details and delete groups.
Release group flow screen
This screen shows detailed information on the releases that are in a release group. From this screen, you can add and remove releases, view the release group schedule, view planned and estimated completion dates. Selecting a release item in this screen will open the release flow screen for an individual release.
Release group actions
Group actions are role based and permissions must be granted to a user or team before they can view, edit, or create release groups.
Grant release group permissions
- On the navigation bar, click Design.
- Click Folders.
- Select a folder.
- From the tab, click Teams & Permissions.
- Under the Folder permissions section, add a team name to the right of View release group and Edit release group.
Note: The edit release group permission is required to create release groups.
Create a new group
- On the navigation bar, click Design.
- Click Folders.
- Select a folder.
- From the tab, click Groups.
- Click New release group.
- Enter a group name.
- Select a start date.
- Select an end date.
- Click Create.
Note: To view groups that are not active, click Status and select the Planned checkbox from the drop-down.
Edit group details
You can edit group details from two locations:
- From the Releases screen:
- On the navigation bar, click Releases.
- Click Groups.
- On the right of a group, click Edit.
- Edit group details.
- Click Save.
- From the Folders screen
- On the navigation bar, click Design.
- Click Folders.
- Select a folder.
- From the tab, click Groups.
- From the tab, click Groups.
- On the right of a group, click Edit.
- Edit group details.
- Click Save.
Note: To view groups that are not active, click Status and select the Planned checkbox from the drop-down.
Add a release to a group
- On the navigation bar, click Releases.
- On the right of the release, click
.
- Click Add to group.
- In the Group name field, enter a group name, or select a group by clicking the drop-down arrow.
- Click Add.
Add multiple releases to a group
- On the navigation bar, click Design.
- Click Folders.
- Select a folder.
- From the tab, click Groups.
- Select a group.
- Click Add a release.
- Click Select all or select the releases you want to add.
- Click Add.
Remove a release from a group
- On the navigation bar, click Releases.
- Click Groups.
- Click the group name.
- Beside the release name, click
- Click Remove from group.
Delete a group
You can delete a group from two locations:
- From the Release screen:
- On the navigation bar, click Releases.
- Click Groups.
- On the right side of the group, click Delete.
- From the Design screen:
- On the navigation bar, click Design.
- Click Folders.
- Select a folder.
- From the tab, click Groups.
- On the right side of the group, click Delete.
Ordering and displaying groups
Groups are displayed and ordered based on two attributes: Status and Order by. Both attributes are displayed at the top of all release and group pages.
-
To order and display groups based on status: From the Status drop-down, select a checkbox, or checkboxes, based on activity or completion status.
-
To order groups based on risk or date: Select an option from the Order by drop-down.
Status types
All release groups display a current status. The status types are as follows:
- Planned: No release in a release group has started.
- In process: One or more releases in a release group is being executed.
- Paused: All releases in a release group have been paused.
- Failing: One or more releases in a release group is failing.
- Failed: All releases in a release group have failed.
- Aborted: All releases in a release group were aborted.
- Completed: All releases in a release group were completed.