DROPS for Jenkins

Select the release in which to save the artifacts that will be imported.

• If Current Release is selected, the release defined in the Current Release field in the application is used to import (displayed in parentheses).

• If Create a New Release is selected, a new release will be created using the Release Number Template defined in the application.

  If this option is selected, define the part of a release’s version number to increment from the Increment Part drop-down menu. Keep in mind that the algorithm will update the other parts automatically. By default, the part is set to the value defined in the Default Release Increment Part.

• Selecting an existing, active release from the prepopulated list will import the artifacts to that release.

You can create a new release by adding a script via the pipeline. To create a release by providing a release number (or updating an existing release if the number already exists) you must use the Jenkins pipeline. The following is the syntax to follow:

*pipeline {
 agent any

 stages {
  stage('DEMO') {
   steps {
    dropsImport application: [code: 'DEMO'],
      executions: [[component: [code: 'WEBAPP'], externalVersion: '1.0.0.0', strategy: [code: 'WEBAPP_GIT_IMPORT']]],
      {color:#ff0000}release: [$class: 'NamedRelease', number: 'BUILD_${BUILD_NUMBER}']{color},
      releaseDescription: 'my test from pipeline',
      resetRelease: true,
      startAutomatically: true
   }
  }
 }
}*

The *NamedRelease* parameter must be paired with one of the following parameters in order to find the correct release. If the corresponding release exists, the task will update it, if it doesn't exist, Jenkins will create a new release.

1. number: 'the release number' (The number parameter is a String type and can use Jenkins environment variables).
2. releaseID: 'the ID of the existing release'.