RLM create and deploy package instance

You can use this automation script to create and deploy an instance for an existing package on BMC Release Package and Deployment by using the BMC Release Process Management user interface. For this script to work, you must have a created package on BMC Release Package and Deployment.

Inputs required while creating a step

To use this automation script in a step, specify the following inputs:

• Package: Select in a list of packages present in the database of BMC Release Package and Deployment.
• Contents: This item is displayed only after you select a package. Depending on the package you select, the associated references are displayed.
• Route: Select from a list of routes present in the database of BMC Release Package and Deployment.

• Set Properties: This item is displayed only after you select a package. The table displayed provides a list of properties that are associated with the selected package on BMC Release Package and Deployment. You can select one of these properties and override its value with a property value in BMC Release Process Management. For this, you must first create a mapping of properties in BMC Release Process Management with that on BMC Release Package and Deployment. For more information, see Setting-property-values-for-a-package-repository-or-instance.

  Note

  The property values are overridden for the package, not instance, in BMC Release Package and Deployment.
  If you integrate with BMC Release Package and Deployment, the property values are overridden for the instance in BMC Release Package and Deployment. To use this functionality, reimport the RLM create and deploy package instance automation script.

• Locked: To create a locked instance for the selected package, select Yes. Otherwise, select No.

• Environment: A list of environments is populated when you select a route. You can select the route in a list of environments associated with the selected route.

  Note

  If the environment name used in the request of the step matches the environment name on BMC Release Package and Deployment, then such an environment is selected by default in the step and is suffixed with the text (inherited from request).

• Channels: Select the channel for the deployment in the list. A list of channels is populated when you select an environment.
• Log Format: Select the format of the logs returned by the deploy operation from BMC Release Package and Deployment.

Expected results after  running this automation script

After you run this script, you can expect to see the following results on the Automation tab in the step:

• Package Instance: Name of the package instance that is created.
• Package Instance Log: Contains log details about the package instance that is created. You can download this file and save it. This file contains log details that are originally generated in BMC Release Package and Deployment and is available for download from BMC Release Process Management.
• Package Instances: Provides a URL that takes you to the location where the package instance log file is available on BMC Release Package and Deployment.
• Deployment Log File: Contains log details about the package instance deployment. This file contains log details that are originally generated in BMC Release Package and Deployment. You can download the file from BMC Release Process Management.
• Deployment Log URL: Provides a URL that takes you to the location where the deployment log file is available on BMC Release Package and Deployment.

Associated data retriever scripts

The RLM create and deploy package instance local ruby script uses the following data retriever scripts: