Skip to main content

13 docs tagged with "customization"

View all tags

Automatically Handle Failures in Tasks

By default, when a task in a release fails, the release stops so you can retry the task, skip the task, or add new tasks to resolve the issue. If the Abort on failure option is selected, the release immediately aborts if a failure occurs. This is useful for Continuous Integration/Continuous Delivery environments in which a new code commit will fix the problem and start a new release.

Create Custom Configuration Types

In Release you can add custom configuration types in XML. Custom configuration types appear in the configuration screens, and custom tasks can reference configuration instances. You can use custom configuration type tasks to reference third-party component settings. For example, Release includes with JIRA Server and Jenkins Server, which are custom configuration types.

Create Custom Task Types

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. For example, Release includes JIRA integration tasks, which are a set of custom tasks.

Create Custom Trigger Types

You can use triggers to create and start new releases from within Release based on external events that you define. Release includes several defined trigger types that you can choose from the user interface. You can also define a new trigger type and associate it with a script to start releases based on other events.

Creating Custom Tiles

In Digital.ai Release you can customize the release dashboard by adding new tiles as per your specific requirements to know about your planning information. This topic describes how to create custom tiles.

Declare Custom REST Endpoints

You can extend Release by creating new endpoints backed by Jython scripts. You can use this feature, for example, to integrate with other systems.

Release Architecture

Release features a modular architecture that allows you to change and extend components while maintaining a consistent system. This is a high-level overview of the system architecture:

Test an Automated Task During Configuration

When you are configuring an automated task such as a Webhook, Script, or custom task, for the first time while creating a release template in Release, you usually need to test and tweak it a few times before the configuration is correct.

Use Scheduling in Scripts

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, see Create custom task types.

Using Release API in Scripts

Release has an API that you can use to manipulate releases and tasks. You can access the API from Jython Script tasks and from Release plugin scripts. This is an example of a simple Jython script in a Script task. It uses a script to add a comment to the task.

Webhook Event Tasks

Webhook event tasks are extensible automated tasks that wait for events from webhooks endpoints and complete when the incoming event matches the specified condition.