Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

You can move all of the Salesforce organization’s metadata components to a GIT repository branch using the Salesforce Bulk Migration Task. Once the task has been created, run it to select the metadata component types and the target branch to bring in the changes. Opsera will push the code to the configured branch of the repository during complete sync-up and override any components that are present there.

In this section:

  • Create Salesforce Bulk Migration Task

  • Run Salesforce Bulk Migration

Create Salesforce Bulk Migration Task

  1. Login to Opersa, and navigate to Operations > Tasks.

  2. Click New Task.

  3. In the Create New Task popup, enter the following details:




  4. Select Salesforce Bulk Migration from the Type drop down. Once this has been selected, the following values will be fetched for selection:
    Jenkins Tool - Select an established Jenkins tool from the Tool Registry.
    SFDC Account - Select an established Salesforce tool from the Tool Registry.
    Account - Select the configured SCM account that has previously been added in the selected Jenkins tool in the Accounts tab.
    Repository - Select a Repository from the SCM account.
    Branch - Select a branch where the changes will be merged. To create a new branch, toggle Create a new branch ON, provide a new branch name, and select a parent branch. Existing and modified files will be pushed onto this parent branch.

  5. Select Create to save.

  6. After task is created, select Run Task to successfully merge the task.

Run Task Instructions

  1. In the Opsera Task table, select individual task to view Task Details→ and then select Run Task.

  2. In the Opsera Task Confirmation, select a branch:

    Branch: If user wishes to use an existing branch, they can select one from the Branch drop down list.

    Create a new branch: If user wishes to change the branch where files are getting synched they can do so by toggling on Create a new branch. Once this has been toggled on, user will be prompted to provide a branch name and select an Upstream Branch from which the feature branch will be created.

  3. Select Run Task. Proceed to follow the steps in the Salesforce Bulk Migration Wizard, selecting components to be included in the run.

  4. Click ‘Start a New Instance’ button to run the Salesforce Bulk Migration Wizard and select components.

  5. Select components and click ‘Proceed with Selected Components’.

  6. On the Salesforce Bulk Migration Wizard Confirmation Screen, verify the components selected and click ‘Proceed’.

 

Task Activity Logs

Once the Salesforce Bulk Task has been triggered and is running, view the Task Activity Logs to view the components that were retrieved and the total count against each component type. Locate the Run number you wish to monitor and click on ‘console log’ in Log Type column to view.

  • No labels