Parallel Processor

The CI JOBS screen is best viewed when the zoom setting is set to 80% on your chrome/firefox browser.

About Parallel Processor

The Parallel Processor feature allows you to configure POST requests to be fired before or after a deployment request is triggered to Salesforce. For example, to send notifications to the slack channel post a CI Job is triggered.

Where can I find this feature in the AutoRABIT application?

When you're triggering a new CI job, look for the Configure Parallel Processor function under the Deploy > On Successful Deployment section.

Important Note: This feature is currently available for the following CI Jobs:

  1. Deploy from Salesforce Org

  2. Deploy from Salesforce Org with a Version Control backup

  3. Deploy from Version Control

  4. Deploy SFDX source from Version Control

  5. Install an Unlocked Package from a Version Control Branch

Configuring Parallel Processor

  1. Select the checkbox: Configure Parallel Processor

  2. Next, fill in the below details:

    • URL Path (required): The target URL endpoint of the HTTP request

    • Client Id (required): The client ID that your callout service uses to identify the AutoRABIT application

    • Client Secret (required): The client secret that your callout service uses to authenticate the identity of the AutoRABIT applicationThe Client Secret field is hidden during the editing of your current CI job, preventing you from updating the secret key. But you can insert a new secret key (if required).

    • Access token URL (required): The URL that the client uses to obtain an access token given an authorization code

    • Scope (optional): Specifies the level of access that the AutoRABIT application is requesting

    • Grant Type (required): Client Credentials auto-selected by default

    • Version (required): Enter the version here

  3. Click Test Connection to check if the connection has been authenticated or not. A success message is displayed after the authentication is completed.

  4. The Content-Type header describes the format in the body of your request is being sent in. For example, the body of your requests can be sent as JSON or XML.

    1. To send JSON in a request, use application/json and add your content in the body provided

    2. To send XML in a request, use application/xml and add your content in the body provided

  5. Dynamic URL Parameters: AutoRABIT allows you to include the various variables from your AutoRABIT organization, for example, the name of the CI job, build number, etc Dynamic Parameters:

    ParameterDescription

    {projectName}

    Name of the CI Job

    {buildNumber}

    Build Number of your CI Job

    {sforgName}

    Name of your Salesforce Org

Note: You must specify values for dynamic parameters before executing the query, and the types of the specified values must match the expected types.

  1. Request API Version (required): Enter the API versions

  2. To add a custom header, click on the Add Header button and enter the keys and the value to it. Multiple adding of keys and values are allowed.

Default headers is set as "Accept" :"application/json", "Content-Type":"application/json"

  1. Poll Duration (Mins): This allows you to define the polling duration in minutes for the job execution. This field is mandatory. AutoRABIT will perform the HTTP request based on the poll duration chosen and if a 200 OK is returned, it will continue with the next step. If the 200 response code is not seen within the given time frame, You will be shown a timeout message in the log file.

  2. Poll Interval (Mins): Time-bound between two consecutive API calls, for example, 1minute, 5minute. This field is mandatory.

  3. Click on Save.

PreviousCI Job RollbackNextEnabling GitHub Checks

Last updated