Glossary of Release Terms

Activity logs
In Release the activity log shows all the events that occur in a release, providing an audit trail of all the actions performed by users and the related dates and times.
Archive database
In Release all completed releases are stored in a database that is separate from the repository which is known as an archive database.
Blackout period
A scheduled period of time where specific tasks cannot be performed.
In Release blueprints help you to create declarative YAML files that simplify the infrastructure provisioning and application deployment process.
Canary release
Canary Release is a deployment pattern that allows you to roll out new code/features to a small subset of users on your production environment as an initial test.
A set of computers that are inter-connected and work together and viewed as a single system.
Cron pattern
The cron pattern is a list of six fields representing second, minute, hour, day, month, and weekday.
Custom dashboards
Dashboards that are customized as per user requirement.
Custom tasks
In Release you can add custom task types that appear in the user interface and integrate seamlessly with other tasks in the release flow. You can use custom tasks to integrate with third-party components.
Custom tiles
Customization of release dashboard as per user requirement to show the planning information and the details of the release status by adding new tiles.
Dashboard tracks, gathers, and displays the information of the release status.
Delivery patterns
The Delivery Patterns feature in Release allows you to use deliveries and tracked items to synchronize multiple releases together.
Export Hook
Export Hook is a feature in release to configure Release to run a Jython script for every release that is about to be archived. Export hooks can also be used to store all completed releases in an SQL database and later use a reporting tool to query over the data.
Failed Task
A task that has not fulfilled its function.
Folder variables
Variables that are used in all templates and releases inside a specific folder.
Gantt chart
Gantt Chart is used for project management to show the relationships between activities and the current schedule status.
Gate tasks
In Release a Gate task contains conditions that must be fulfilled before the release can continue. There are two types of conditions: simple checkboxes and dependencies on other releases.
Git triggers
In Release Git triggers periodically polls a Git repository and triggers a release when it detects a new commit.
Global variables
Variables that are used in all templates and releases.
Keycloak is an Identity and Access Management solution which is used for OpenId Connect to login in Release.
Kubernetes Operator
Controller used to deploy Deploy and Release applications on various platforms, such as Amazon EKS, Azure AKS, and OpenShift on AWS clusters. See Kubernetes Operator.
LDAP repository
LDAP (Lightweight Directory Access Protocol) is a set of open and cross-platform protocols used for directory services authentication.
Load balancer
A load balancer distributes the incoming traffic among the servers to make the network faster.
In Release machine learning is used to predict failed release or task, or how much time it will take to execute it before releases even start.
Maintenance window
A pre-scheduled time designated in advance by the technical staff to perform the maintenance of Software or hardware.
Network Time Protocol (NTP) synchronization
NTP protocol is used to synchronize computer clock times in a network.
Nexus triggers
In Release Nexus trigger allows Release to interact with Sonatype Nexus repositories. It uses the Nexus Server REST API to communicate and fetch information from Nexus repositories.
Pipeline Orchestrator
Pipeline Orchestrator is an automated process and tool that allow developers and operations teams to build and deploy code to the production environment and gives the overall perceptibility of the Release Pipeline.
Part of code or software which is ready and has the ability to meet the demands of customers and users.
A quorum is the minimum number of votes that a distributed transaction has to obtain in order to be allowed to perform an operation in a distributed system.
A release is divided into phases, which represent logical stages in the process that must happen in succession. For example, a release could include Development, QA, and Deployment phases. In Release, a phase is a grouping of tasks, which are the activities that must be done to fulfil the release.
Release Archiving
Release archiving is the record of completed and archived releases. See Release Archiving.
Release Flow
Release flow is started by the Release application at the start of the release. The Release flow is the workflow of the release. The Release application determines the current task that needs to be picked up, and executes it if it is an automated task, or sends a message to the intended recipients in case of manual tasks.
Release flow editor
In Release the release flow editor shows the phases and tasks in the release. You can use this view to add, move, edit, and delete phases and tasks.
Release overview
The release overview shows the list of releases that you have permission to view and that are planned, active, or completed.
Release Owner
Release owner is responsible for the correct performance of the release. If anything goes wrong, the release owner is notified. For example, the release owner is notified if the person handling the task indicates there is an issue, or if there is an error encountered during an automated task.
Release permission
In Release you can use release permission to assign permissions to teams on folders, top-level templates, and top-level releases.
Release plugins
Release plugins are add-ons or extensions to provide support for various third-party tools.
Release templates
In Release, Release templates are like blueprints. You can use templates to model the ideal process of a release flow.
Release value stream
In Release the release value stream focuses on improving the quality of completed and aborted releases.
Release variables
Variables that are used in a specific template or release.
Risk profile
In Release all completed releases are stored in a database that is separate from the repository which is known as an archive database.
Scheduled script
In Release a scheduled script can be used within a custom task script to check for the availability of a resource or to do something when conditions are satisfied.
SVN triggers
In Release SVN triggers periodically polls a Subversion repository and triggers a release when it detects a new commit.
System message
Any delivery status notifications displayed on the screen like non delivery reports (NDR’s), bunce messages, quota messages.
Set of steps performed in a workflow to complete the work.
A template is a blueprint for the release. You can use the template to start different releases that have the same flow.
In Release triggers allow you to set the conditions for an event to create an action, such as a release task.
A variable is a value provided in the template. Variables are identified by the ${ } syntax. Examples: text, password, number, and list.
Webhooks in Release is able to trigger releases as a reaction to specific HTTP requests made by an external source.
Work directory
In Release work directory is used to store temporary data that cannot be stored in the memory. For example, the files that are temporarily stored in the working directory are being uploaded when configuration items (CIs) are being created.