Digital.ai Release is a release orchestration platform. It lets teams plan, track, and execute releases from a single location, giving every stakeholder — developers, QA engineers, release managers, and operations teams — a consistent view of release status.
Using a Git trigger you can start a release from a Git repository.
Release triggers are an automated way to create and run a release. When you create a trigger for a release template and enable it, Release will execute the script associated with the trigger at a specified interval. When the trigger starts, it will create and start a new release from the template. A good example of a trigger is one that polls a source code management system like GitHub for a change and starts a release as a result.
Deployment event triggers listen to events from status event sources and deployment providers to start releases. Each time a Deployment provider application that existing Live Deployments in the Release server changes its state, the trigger will start a release from the template that is associated with the trigger.
The Release Git trigger periodically polls a Git repository and triggers a release when it detects a new commit.
The Release JFrog trigger allows Release to interact with JFrog repositories. It uses the Jfrog REST API to communicate and fetch information from JFrog repositories.
This topic describes how to navigate to triggers in Digital.ai Release, including both generic navigation and specific navigation within folders.
The 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.
The Release SVN trigger periodically polls a Subversion repository and triggers a release when it detects a new commit.
This topic explains how to configure and manage the Time: Schedule trigger in Release.
Webhook event triggers listen to events from event sources such as webhook endpoints and deployment providers to start releases.