DROPS for JIRA Cloud

The DROPS for JIRA Cloud add-on allows you to create and execute import and deployment requests via your JIRA Cloud projects and issues.

In the Apps management section, click the Upload app link and enter the following app descriptor URL to upload the app and install:

https://drops-jira-cloud.arcadsoftware.com

Click Upload.

Reference

For more information about installing add-ons with the UMP, refer to the Atlassian Universal Plugin Manager documentation.

The server connection form in the App management section is used to ensure that the connectivity with the DROPS Server is successful. This task is an administrative task to finalize the installation of the add-on.

  • To configure the connection to a DROPS Server, go to Apps menu > DROPS Release Manager > DROPS Server Configuration.
  • Define the DROPS Server URL, the User and the Password to connect to the server. Click Save.
  • Click Test connection to ensure the app is correctly connected to the DROPS Server.

The access to the DROPS Server is defined for each user in the user preferences. The DROPS users access the server with their own credentials.

  • To configure the access to the DROPS Server go to [your user profile] > DROPS Credentials.
  • Define the DROPS Server URL, the User and the Password to connect to the server. Click Save.
  • Click Test connection to ensure the app is correctly connected to the DROPS Server.

You must have project administrator privileges to configure the permissions for the DROPS app.

The DROPS for JIRA Cloud app has the following project permissions:

DROPS application mapping
Configuring DROPS application mapping in project configuration.
DROPS environment mapping
Configuring DROPS environment mapping for deployment in project configuration.
DROPS release deployment from project
Creating DROPS deployments from the project.
DROPS release imports from project
Creating DROPS imports from the project.

The DROPS for JIRA app has the following issue permissions:

DROPS release deployment from issues
Creating DROPS deployment from issues.
DROPS release import from issues
Creating DROPS import from issues.

Configure these permissions according to the permissions schema you use for your projects. The application and environment mapping permissions allow to link projects to DROPS applications and environments and the other permissions allow the creation of import instances and deployment instances at project or issue levels.

Example

For a development project which creates versions of an application:

  • project administrators can map to a DROPS Application,
  • project manager can create import instances from JIRA versions at project level,
  • no grants to deployments permissions/environment mapping.
Example

For a project dedicated to deployments:

  • project administrators can map to DROPS environments,
  • users can create deployment instances from DROPS Releases at issue level,
  • no grants to imports permissions/application mapping.

The new JIRA permissions schemas coupled to DROPS existing permissions gives to administrators the flexibility to configure applications access and roles/rights to applications/environments.

This procedure maps a JIRA project to a DROPS application and is mandatory for import actions. When configured, it also limits deployments processes to this application.

To configure the application mapping, go to Project settings > DROPS Import.

Select a DROPS Application in the list and click Save.

This procedure maps a JIRA project to DROPS environments and is mandatory for deployment actions. When configured, it limits where deployments processes can be launched.

To configure the application mapping, go to Project settings > DROPS Deploy.

Select one or several DROPS Environments in the list and click Save.

Go to Project > DROPS Import.

The DROPS import view shows all the import instances for the mapped DROPS Application.

Each line represents an import instance with relevant information like statuses, dates, releases number and description. The colors reflect the different statuses of the instances. Click the Log icon to download the full formatted log of the instance when the status is completed.

To create a new import instance, click the [...] Action button and select the Create DROPS Import action.

Define the necessary elements to create a new import instance and click Create.

Version
The JIRA version for which you can create a DROPS Release. The JIRA version name must be the same as the DROPS Release number.
Description
A description of the release you are about to create or modify it already exists.
Reset release
Tick the Reset release option to empty an already existing release before the import instance execution (used only if the release already exists).
Strategy
All the import strategies for all the application components you can activate/deactivate and give the external version if needed (default value is *RELEASE like in the DROPS Studio).

The import instance is executed as soon as it is created.

For a JIRA issue, the DROPS tasks are available in the right-hand panel.

Click DROPS imports to show the past imports linked to the JIRA issue.

The list is filtered by the Application mapping and the fix versions of the issue and show the status and date of each import instance. Clicking the Log icon allows to download the full formatted logs.

To create a new import instance, click the [...] Action button and select the Create DROPS Import action.

Define the necessary elements to create a new import instance and click Create.

Version
The JIRA version for which you can create a DROPS Release. The JIRA version name must be the same as the DROPS Release number.
Description
A description of the release you are about to create or modify it already exists.
Reset release
Tick the Reset release option to empty an already existing release before the import instance execution (used only if the release already exists).
Strategy
All the import strategies for all the application components you can activate/deactivate and give the external version if needed (default value is *RELEASE like in the DROPS Studio).

The import instance is executed as soon as it is created.

Go to Project > DROPS Deployments.

The DROPS Deployments view shows all the deployments instances for the mapped DROPS environments. This list can be filtered (limited) to one application if an Application Mapping is configured.

Each line represents a deployment instance with relevant information like statuses, dates, applications and releases number, target environments. The colors reflect the different statuses of the instances. Click the Log icon to download the full formatted log of the instance when the status is completed.

To create a new deployment instance, click the [...] Action button and select the Create DROPS Deployment action.

Define the necessary elements to create a new deployment instance and click Create.

Environment
The list shows all the available DROPS environments.
Processes

The list shows all the processes for each DROPS environment.

Release

The list shows all the release to deploy for each deployment process.

Transaction ID.
The transaction ID to use (like for the deployments from the DROPS Studio). Use a static format in addition to variables to create IDs your team will recognize.

The deployment instance is executed as soon as it is created.

For a JIRA issue, the DROPS tasks are available in the right-hand panel.

Click DROPS deployment to show the past deployments for the mapped environments of the project.

The list is filtered by the Application mapping and the fix versions of the issue and show the status and date of each deployment instance. Clicking the Log icon allows to download the full formatted logs.

To create a new deployment instance, click the [...] Action button and select the Create DROPS Deployment action.

Define the necessary elements to create a new deployment instance and click Create.

Environment
The list shows all the available DROPS environments.
Processes

The list shows all the processes for each DROPS environment.

Release

The list shows all the release to deploy for each deployment process.

Transaction ID.
The transaction ID to use (like for the deployments from the DROPS Studio). Use a static format in addition to variables to create IDs your team will recognize.

The deployment instance is executed as soon as it is created.