DA Deployment

The DA Deployment bundled plugin integrates PulseUno with Deployment Automation (DA) to publish and deploy artifacts from a Dimensions CM stream.

Prerequisites

The DA Deployment plugin enables you to automate the path to production for your application:

  • Publish files from a stream to a Deployment Automation server as a new component version.

  • Add a Deployment Automation status to a new published version.

  • Deploy the new published version.

Before you can use the plugin in a chain, ensure that you fulfill the following prerequisites:

  • Install the Deployment Automation server in a network location where the plugin can connect to. For details about supported versions, see the Support Matrix.

Back to top

Create server configuration file

Typically, the following DA Deployment plugin properties file is required:

${dataDir}/conf/experts/com.serena.starlight/sdadeploy/sda-pulse-expert.properties

The following property identifies the location of the Deployment Automation server. If the default URL is correct, you do not need to edit it:

Property Description
sdaServerUrl

The URL of the Deployment Automation server web application.

Default: http://localhost:8080/da

Back to top

Configure plugin settings

Because Deployment Automation normally operates on binary files, add the DA Deployment plugin to a chain that populates a workspace with built artifacts.

When you add the DA Deployment plugin to a chain, specify the following configuration details:

Field Description
Title Enter a name for the plugin step. Default: DA Deployment.
Username Enter the username of a Deployment Automation server administrator.
Password Enter the password of the Deployment Automation server administrator.
DA Server URL Enter the URL of the Deployment Automation server web application.
Component Name

Enter the name of the Deployment Automation component that will be published.

Specify the format of the component name to make it easier to identify its source. You can enter the value as one of the following variables, using the syntax {{variable_name}}:

  • CHAINNUM

  • SUITE_NAME

  • CHANGESET_ID

  • PRODUCT_NAME

  • STREAM_NAME

  • STREAM_VERSION

For example: COMPONENT_NAME-{{CHANGESET_ID}}

Version

A new version of a Deployment Automation component is created each time the plugin runs.

Specify the format of the version name to make it easier to identify its source. You can use the same variables as for the Component Name, for example:

VERSION_NAME-{{CHANGESET_ID}}

Artifact Directory Enter the relative path to the source directory where the artifacts are located, for example, source\.
Include (Optional) To publish only specific files, enter one or more Ant patterns, one pattern per line. To publish all files, leave this field empty.
Exclude (Optional) To exclude specific files from being published, enter one or more Ant patterns, one pattern per line. To publish all files, leave this field empty.
Add Status

(Optional) Select this option to add status to the new component version.

In the Status Name field, enter the Deployment Automation status to move the new component version to, for example, STATUS_SUCCESS.

Deploy

(Optional) Select this option to specify how the new component version will be deployed:

  • Application name. Specify a Deployment Automation application (contains a component to be deployed).

  • Application process name. Specify the name of Deployment Automation application process to run.

  • Environment Name. Specify the Deployment Automation environment in which the application process will run.

  • Deploy Properties. Specify deploy properties for running the Deployment Automation application process.

    Enter each name=value pair on a new line, for example:

    set_up_db=true

    use_logging_level=trace

Back to top

See also: