This plug-in enables Jenkins to interact with Embotics Commander.
It provides the following build steps:
Request New Service
Wait For Service Request Completion
Run Command Workflow
Wait For Command Workflow Completion
Request New Service build step enables Jenkins to request a service from Embotics Commander.
To request a service (for example, a VM), enter the name of a preconfigured Commander service and look it up. If the service is found, it's returned as a JSON payload. You may adjust the configuration parameters of the payload as required. You may also modify the default timeout and polling intervals before making the service request.
This action can be executed synchronously or asynchronously.
If asynchronously execution is configured, a following wait build step can check the results of this step.
After the request is made, the following environment variables are created:
VCOMMANDER_REQUESTED_SERVICE_ID - the request ID
For a synchronous execution, the build log will provide details about the service request. If the request is successful, the following environment variables are created:
VCOMMANDER_REQUESTED_SERVICEx_COMPONENTy_NAME - The deployed component name, where x is the service index and y is the component index.
VCOMMANDER_REQUESTED_SERVICEx_COMPONENTy_TYPE - The deployed component type, where x is the service index and y is the component index.
Indexes start from 1.
Wait For Service Request Completion build step enables Jenkins to wait for the completion of an asynchronously-called Commander Request.
The environment variable VCOMMANDER_REQUESTED_SERVICE_ID created by that service request step can be used as input parameter for this wait build step.
The build log will provide details about the service request. If the request is successful, the following environment variables are created:
VCOMMANDER_REQUESTED_SERVICEx_COMPONENTy_NAME - The deployed component name, where x is the service index and y is the component index.
VCOMMANDER_REQUESTED_SERVICEx_COMPONENTy_TYPE - The deployed component type, where x is the service index and y is the component index.
Indexes start from 1.
Run Command Workflow build step enables Jenkins to run a command workflow in Commander.
To run a command workflow, enter the name of the workflow and target.
This action can be executed synchronously or asynchronously.
If asynchronously execution is configured, a following wait build step can check the results of this step.
After the workflow request is made, the following environment variables are created:
VCOMMANDER_WORKFLOW_TASK_ID - the task ID running the workflow
For a synchronously execution, the build log will provide details about the command workflow.
Wait For Command Workflow Completion build step enables Jenkins to wait for previous asynchronously called Commander Run Command Workflow completion.
The environment variable VCOMMANDER_WORKFLOW_TASK_ID created by the previous step can be used as input parameter for this build step.
The build log will provide details about the command workflow.
All the created environment variables can be used in subsequent build steps within the same project.