Manage Applications

In this article, you’ll learn how to set up applications and deployments in Golive. For a deeper understanding about these concepts, refer to the Understand Environment Core Concepts article.

Requirements

You’ll need Manage Applications global permission to perform operations on applications. For more details on permissions, refer to the Permissions article.

Setting up an Application

To set up an application in Golive, follow these steps:

1. In Golive, Click the gear icon located on the upper right corner of Golive Pages.

2. From the drop-down menu, select Golive Settings.

3. In the Applications section, select Applications List.

4. Click the Add Application button located at the top right corner of the Applications page.

4. Choose a name for your new application.

5. Click Create.

Jira Versions Tab

The Jira Versions tab controls how application versions are mapped to Jira Versions, also called Jira Releases, and how Golive updates the Fix Versions field of deployed work items.

Primary Jira Space

Select the Jira space that acts as the source of truth for the application versions.

When a primary Jira space is selected and a new deployment is created from Golive:

• Golive suggests versions from that space.

• Golive creates a new version in that space when the user recording the deployment has the Manage Versions permission. This happens even when the deployment does not contain any work item from the primary space.

Leave this field empty if the application versions should not be managed in a specific Jira space.

Version Name Prefix

Optionally define a prefix used to create and match Jira Versions.

Golive only suggests versions whose names start with this prefix. When Golive creates a version, it automatically adds the prefix if it is not already included in the version name.

Trailing spaces are significant. For example, with the prefix ECOM , the application version 1.2 is created as ECOM 1.2.

Fix Version Updates

Choose how Golive updates the Fix Versions field when deployments are recorded:

• Do not update Fix Versions: Golive does not modify the Fix Versions field of deployed work items.

• Update Fix Versions in the primary Jira space only: Golive updates work items belonging to the primary Jira space.

• Update Fix Versions in all deployed work item spaces: Golive updates work items in every Jira space referenced by the deployment.

With the last option, Golive automatically creates the missing Jira Version in another space when:

• The deployment contains at least one work item from that space.

• The user has permission to create versions in that space.

• The matching version does not already exist.

The selected primary Jira space remains the source of truth for the application versions.

Deployments Tab

The Deployment Settings tab allows you to choose how you want to manage deployments of your application in Golive. Follow these steps to configure your application deployment management.

1. Within the Application dialog, navigate to the Deployments tab.

2. Choose which information should be displayed and editable when performing a new deployment from Golive screens:

• Show build number: Enable this option when you need to distinguish different builds of a same version.

• Show description: Enable this option to set a description for your deployment. This field supports basic HTML tags for rich content, and is unlimited in size.

• Enable edition of deployed issues: When enabled, users will be able to add/remove deployed issues when creating or editing a deployment in Golive.

3. Define customizable Deployment Attributes to store additional information in each of your application deployments.

4. Choose whether to enable Track re-deployments of the same version. By default, Golive merges two successive deployments of the same version with the same build number to a a given environment.

Tip

The best practice is to use different build numbers to track successive deployments of the same version (e.g., common when working with "snapshot" releases).

Application Tiers Tab

To configure an application composed of multiple tiers, tenants, components, modules or markets, follow these steps:

1. Within the Application dialog, navigate to the Applicaton Tiers tab.

2. Add, remove and re-order the list of application tiers in the Application Tiers field.

3. Once at least one application tier is set up at the application level, you'll be able to add a Tier at the environment level.

After adding tiers, you can browse and edit the created application tiers from the list of applications on the Applications page

To manage all existing application tiers, including orphaned ones, click Application Tiers located at the top of the Applications page. This will allow you to manage all your application tiers from the Application Tiers page.

Dependencies Tab

To set up dependencies of a current application, follow these steps:

1. Within the application dialog, navigate to the Dependencies tab.

2. Enter a dependency.

3. When at least one dependency is setup at application level, you’ll be able to add dependencies at the environment level.

Converting Application Tiers ↔︎ Application

Convert an Application into Application Tiers

To convert existing applications into application tiers, follow these steps:

1. Go to the Applications page.

2. Locate the application you want to convert.

3. Click the Convert to tier button corresponding to the application. This button is located in the last column of the application row.

Convert Application Tiers into an Application

To convert existing application tiers into applications, follow these steps::

1. Go to the Applications Tiers page.

2. Locate the application tier you want to convert.

3. Click the Convert to application button corresponding to the application tier. This button is located in the last column of the application tier row.