Deployer

3 minute read

You can configure your Deployer tool now.

Deployer configuration

Drag and drop your Deployer and configure the following deployer options on the right pane:

  • Select the Application Radio Button to configure the following parameters on the right pane:

    • App Deployer Configuration: Enables you to configure where you want to deploy the application.

      • Environment Name*: Select the environment from the drop down to deploy the application.

      • Deployment Tool Name*: Select the Deployment (CI) tool name.

      • Job Name*: Enter the job name.

    • Job Parameters:Enter the parameters the job expects.

      • Build: Enter the build name.

      • ENV Name: Enter the environment name.

      • Namespace: Enter the namespace for the environment.

      • Branch Name: Enter the branch name.

  • Select the Infrastructure Radio Button to configure the following parameters on the right pane:

    deployer
    • Environment Name*: Select the environment from the drop down to deploy the application.

    • Deployment Tool Name*: Select the Deployment (CI) tool name.

    • Job Name*: Enter the job name.

    • Job Parameters:Enter the parameters the job expects.

      • Build: Enter the build name.

      • ENV Name: Enter the environment name.

      • Namespace: Enter the namespace for the environment.

      • Branch Name: Enter the branch name.

Modify parameters during execution

Enable Modify Parameters during Execution in the right pane allows you to to modify the parameter of the tool during the pipeline execution.

Deployment verification

Enable Deployment Verification to verify whether any critical problem arises in the process for a specific duration during the pipeline execution.

deployment

Rollback

Enable Rollback allows you to rollback the commit during the pipeline execution.

  • Associated Job*: Select the job from the drop down.

  • Assigned Users*: Select the users from the drop down.

Schedule

  • Enable the check box for a custom script to run at a specific time when a commit happens. You can schedule in the following ways:

    • Force Start: Enable the force start if you need to run the pipeline before Schedule time.

    • Every: Enable the checkbox and select the time (in minutes or hours) to run a custom script.

    • Time: Enter a specific time. When a commit happens, the custom script step waits until the defined time and runs at the specified time.

    • Time Zone: Enter the time zone. The custom script runs at the defined time and in the specified time zone.

    • Recurrence: Enable the check box and define a weekly recurring interval for a custom script to run on a specific day of the week, when a commit happens.

Notification

  • Enable the check box to notify the user upon the completion of a custom script.

    • Success: Enable the check box to notify the user when a custom script is successful.

    • Failure: Enable the check box to notify the user when a custom script has failed.

    • Notify Committer: Enable the check box to notify the user who made the code change and committed. The platform automatically identifies the user who has committed the code change and notifies the committer.

    • Mode: Select the mode of notification

      • Email ID: Select the mail ID of any specific user from the drop down to send the notification.

      • Slack: When you want to get notification on the Slack tool, you can select Slack → Slack endpoint and Slack Channel.

      • Send Event to Observability Tool: You can also choose to send notifications on the Observability tool by selecting the Send event to Observability tool→ Tool name*.

All the fields marked in Asterisk (*) are mandatory.

AWS ECS: CloudBees Release Orchestration SaaS supports Amazon Elastic container service to deploy your docker application in the specified environment.

Kubernetes Deployment: CloudBees Release Orchestration SaaS supports Helm and Kubectl to deploy your docker application in the specified kubernetes environment.