Learn how to setup applications and deployments that are Golive Core Concepts:
What is an Application?
An application describes the type of service that is hosted by a given environment.
This can either be a business application (ex: eCommerce, Payment Services,SAP,...) or a technical service (ex: Kubernetes, OS,…).
An application can have dependencies with other applications and may be composed of multiple application tiers.
The deployment specify the version of the application that is currently deployed to an environment.
Access the Applications page from the Settings menu of a Golive Page to perform all operations on your applications:
You need to have Manage Applications global permission in order to perform operations on applications. Learn more about Security & Permissions
Create/Edit an Application
Click on Add Application button on the top right corner of the Applications page (or on the “Pencil” icon next to the Application you want to edit):
Choose a name for your new application:
The edition dialog will open:
Follow instructions in following section in order to configure your new application.
You can re-use and synchronize versions of your application with Jira releases managed by one or multiple Jira projects. You can setup this integration in the “Jira Versions” section:
Configure in which Jira Project(s) environments of current application will find and store their deployed versions:
None: deployed versions will not be linked to any Jira Release
All: deployed versions can be linked to any Jira Release
Selected project: deployed versions can be linked to a Jira release of the selected Jira Project
Version Naming Convention
The selected Jira Project may contain versions of different applications. It is possible to use a naming convention and to use a prefix to distinguish versions of different applications:
Synchronization of Jira Version
You can keep Golive deployed version in sync with Jira Versions:
If this option is enabled:
the deployed versions created in Golive are automatically created in the corresponding Jira project
when deploying an existing Jira version, the list of Jira Issues “fixed in” the selected version are automatically added to the new Golive deployment
in the other direction, when Jira issues are added to a deployed version in Golive, they are automatically pushed as “fixed in” the linked Jira Version
Example: mapped Jira versions will be selectable when creating or updating a deployment to an environment:
Check next section to learn more about application deployment settings
This section lets you choose how you want to manage deployments of your application in Golive:
You can 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 in order to set a description for your deployment. This field is unlimited in size and supports basic HTML tags for rich content
“Enable edition of deployed issues”: when enabled, users will be able to add/remove deployed issues when creating or editing a deployment in Golive UI
Example of new deployment creation with “Enable edition of deployed issues” activated:
On top of pre-defined fiels, you can also define customizable Deployment Attributes in order to store additional information in each of your application deployments:
Custom Deployment Attributes
If you cannot find the deployment attributes you need in the pre-defined list, you can setup custom Deployment Attributes from the Applications configuration screen:
In order to add a new attribute, click on “Add Attribute”:
Choose a name and decide if it should be secured (if selected, the value will be hidden by default and accessible only to people with view/edit secured attributes permissions).
Track re-deployments of the same version
By default, Golive merges 2 successive deployments of the same version with the same build number to a a given environment. This avoid pollution of your deployment logs.
Activate this option only if you absolutely need to keep track of every successive re-deployment of the same version and the same build number in your deployment history.
The best practice is to use different build numbers to track successive deployments of the same version (ex: common when working with “snapshot” releases)
You can setup dependencies of current application in “Dependencies” section (learn more about application & environment dependencies):
You can add/remove and re-order dependencies from here.
When at least 1 dependency is setup at application level, you will be able add dependencies at environment level:
You can setup application composed of multiple tiers, tenants, market, modules, components,… (learn more about multi tiers and multi tenancy) by adding “Application Tiers” to your application:
You can add / remove and re-order the list of application tiers from here.
When at least 1 Application Tier is setup at application level, you will be able add “Tier” at environment level:
Browse and edit Application Tier used by an application
Once added, you can easily browse and edit the created Application Tiers from the list of the applications:
Manage all Application Tiers
To manage all existing Application Tiers (including the orphan ones), click the “Application Tiers” top button:
You will be then be able to easily manage all your Application Tiers from here:
Converting Application Tiers ↔︎ Application
You can convert existing applications into application tiers from the Applications page:
N.B. You must first remove existing application tiers of an application prior to be able to convert it to application tiers.
You can convert existing application tiers into applications from the Application Tiers page:
You can only convert application tiers that are not already used by an application.