Using Scripts to Automate Release Process Tasks

You can write your own Groovy scripts to automate release process tasks. Sample scripts to help you get started are located here:

{SBM}Common\Tomcat 7.0\server\default\webapps\rlc\WEB-INF\classes\scripts\Samples

createReleasePackageSample.groovy

This sample script:

• Creates release packages and relates artefacts (deployment units) and corresponding tasks.
• Relates multiple artifacts to a single task and uses a single artefact in multiple tasks.

Limitations:

• All artifacts must use the same configuration, identified by Provider Instance UUID.

• Strings Params 0,1 and 7 are required.
• Strings Params 2-6 may not be passed if a release package has the correct default values for configured fields.
• String Params 8 is optional. The default project is RM_RLM_TURNOVERS.TURNOVERS.

Example:

 {
   "stringParam0": "Release Package Name",
   "stringParam1": "Release Package Description",
   "stringParam2": "Release Type Name",
   "stringParam3": "Deployment Path Name",
   "stringParam4": "Task Template Name",
   "stringParam5": "Release Manager Name",
   "stringParam6": "Release Engineer Name",
   "stringParam7": "Provider Instance UUID",
   "stringParam8": "Release Package Project",
   "arrayParam0": {
      "items": ["artifactId1", "artifactId1", "artifactId2"]
   },
   "arrayParam1": {
      "items": ["Task Title1", "Task Title2", "Task Title2"]
   },
   "path": "createReleasePackageSample.groovy",
   "version": "Samples"
 }

Results:

configureTaskCollectionSample.groovy

This sample script:

• Relates artifacts (deployment units) and corresponding tasks.
• Relates multiple artifacts to a single task and uses a single artefact in multiple tasks.

Limitations:

• All artifacts must use the same configuration, identified by Provider Instance UUID.

• Strings Params 0 and 1 are required.

Example:

 {
   "stringParam0": "Task Collection Id",
   "stringParam1": "Provider Instance UUID",
   "arrayParam0": {
      "items": ["artifactId1", "artifactId1", "artifactId2"]
   },
   "arrayParam1": {
      "items": ["Task Title1", "Task Title2", "Task Title2"]
   },
   "path": "configureTaskCollectionSample.groovy",
   "version": "Samples"
 }

Results:

Artifact IDs

You must pass the correct artifact ID to each plugin:

• Dimensions Baseline

  ID: Dimensions CM Baseline UID

  Type: Long numeric

  Example: 126834642

• Dimensions Request

  ID: Dimensions CM Request UID

  Type: String

  Example: DMPROD_SBMCR_52737

• Jira Issue

  ID: Jira Issue Key

  Type: String

  Example: RLC-183

• Octane Work Item

  ID: EntityType:EntityId

  Type: Compound string

  Example: feature:1010

• Octane Requirement

  ID: EntityType:EntityId

  Type: Compound string

  Example: requirement_document:1005

• SBM Item

  ID: SBM Item's TableIdItemId

  Type: String

  Example: 1010:1230

• SDA Component

  ID: SDA Component ID / SDA Component Version Id

  Type: Compound string

  Example: 7ab6dddb-a5e8-43d3-be64-5721ac92507b/e9d1de49-4c23-4333-b818-971c67fef3d1

• SDA Snapshot

  ID: SDA Snapshot ID

  Type: UUID

  Example: 18f31a3c-e1e5-11e8-9f32-f2801f1b9fd1

• SNOW Item

  ID: SNOW Table / SNOW Item Id

  Type: Compound string

  Example: tableName/sys_id

• Silk Central

  ID: Execution Plan Id

  Type: Integer

  Example: 121244

• ZMF Package

  ID: ZMF Package Name

  Type: String

  Example: ARM1000070