How Deployment Tasks are Handled for Use Cases

After creating the deployment tasks, we can execute them using the Start Deploy transition. The result depends on the plugin configuration settings.

See Use Cases for the Jenkins Plugin for details on the use cases referenced in the following information.

• If you don't have access to Jenkins:
  • Use Cases 1 and 5:

    After Start Deploy, the deployment task will be marked as "COMPLETED" immediately without storing the link to Jenkins.

  • Use Cases 3 and 7:

    After Start Deploy, the deployment task will be marked as "IN_PROGRESS". After polling, the task will be marked as "COMPLETED" if the Jenkins job was started with the Jenkins URL and as "FAILED" if not. You can increase the polling period in the configuration if needed to start the Jenkins job with the URL. The Jenkins build URL will be stored in the Release Control task execution if the Jenkins job was started.

• If you have access to Jenkins and the Jenkins queue is not very long:
  • Use Cases 4 and 8:

    After Start Deploy, the deployment task will be marked as "NOT_STARTED" . After polling, the task will be marked as "IN_PROGRESS" if the Jenkins job was started with the Jenkins URL and as "FAILED" if not. You can increase the polling period in the configuration if needed to start the Jenkins job with the URL. The Jenkins build URL and build number will be stored in the Release Control task execution if needed to start the Jenkins job with the URL. After the Jenkins build is completed or aborted, the rlc_trigger.groovy script will move the task to the "COMPLETED" or "FAILED" state respectively. .

• If you have access to Jenkins and the Jenkins queue is very long and time-intensive, where using polling is unrealistic:
  • Use Case 6:

    After Start Deploy, the deployment task will be marked as "PENDING" and the execution ID will be generated in the provider and passed to the proper Jenkins field. When the job is started in Jenkins, the rlc_start.groovy script will move the task to the "IN_PROGRESS" state and update the execution URL in Release Control. After the Jenkins build is completed or aborted, the rlc_trigger.groovy script will move the task to the "COMPLETED" or "FAILED" state respectively.