Go-RapidDeploy plugins enable Go server integration with RapidDeploy framework, so you can run advanced RapidDeploy middleware orchestrations as part of your pipelines in Go.

You can download the plugin jar files from MidVision github repository, and drop them into your Go-server installation under plugins/external.

This package material plugin can connect to a remote RapidDeploy server, and fetch the packages for the specified project.

The repository configuration will require the remote RapidDeploy server url, an authentication token, and a project name, which will identify the rest of the configuration for the artifact repository to connect. You can generate the authentication token by running a utility script in the RapidDeploy server home under tools directory called run-web-service-encrypter.sh(bat).

Once the repository configuration is done, you can create a RapidDeploy package. The package identifier string will search among the available packages, and return the latest.

Example:

Available packages in the RapidDeploy repository:

jpetstore-0.0.3.ear

jpetstore-0.0.2.ear

jpetstore-0.0.1.ear

Package identifier 'jpetstore' will always return the latest package, in this case jpetstore-0.0.3.ear.

For specific versions, add the version number to the identifier: 'jpetstore-0.0.2' will return jpetstore-0.0.2.ear.

This task plugin can invoke a remote RapidDeploy server, and build a deployment package for the specified project. The deployment package will automatically get the default name (configured in RapidDeploy), and the latest version number.

This task plugin can connect to a remote RapidDeploy server, and run a deployment synchronously with providing the deployment log output in Go.

Note that you will need to have a RapidDeploy package repository plugin configured in your pipeline, pointing to a package, in order to run this task.

To specify the deployment package, you will need to enter the name references of the RapidDeploy package repository plugin Repository and Package name (from the current pipeline) to the last two fields of the task parameters.

For the task configuration, the environment string can be provided by appending the RapidDeploy target object names with a '.' character between each of them. RapidDeploy target definitions are built by four objects: Server, Environment, Instance, Application, which will be identified in Go as: [servername].[environmentname].[instancename].[applicationname]

(Note: from RapidDeploy version 3.5+ only three object is required, as instance is not present in the configuration any more)