# Deploying a Package from a Salesforce Org

{% hint style="info" %}
The **CI Jobs** screen is best viewed when the zoom setting is set to **80%** on your Chrome/Firefox browser.
{% endhint %}

Why Does Salesforce Recommend Moving From SFDX to SFCLI? Click [here](/product-guides/arm/troubleshoot/known-issues-limitations/salesforce-known-limitations.md#why-does-salesforce-recommend-moving-from-sfdx-to-sfcli) for more info.

### Overview <a href="#overview" id="overview"></a>

Back up your Salesforce metadata to version control and trigger a deployment to a Salesforce org based on a **Start Date**. This job can be further customized to run functional test cases from version control.

### Procedure <a href="#procedure" id="procedure"></a>

1. Log in to your ARM account.
2. From the top navigation pane, navigate to **Create New > New CI Job**.

   <figure><img src="/files/cjoXDj7Lgt5rJ3Wz13ND" alt="Create New ➜ New CI Job"><figcaption><p>Create New ➜ New CI Job</p></figcaption></figure>
3. Choose the tile: **Deploy From Salesforce Org**

   <figure><img src="/files/WK1SY4AT5yCCiQNJRrKI" alt="Deploy From Salesforce Org tile"><figcaption><p>Deploy From Salesforce Org tile</p></figcaption></figure>
4. Enter a descriptive **Job Name**.
5. Add a brief **Description**.
6. (Optional) Choose a **Group** to organize the job, or click **`+`** to create a new group.
7. The configuration page is divided into sections explained below.

#### Build <a href="#build" id="build"></a>

Under **Build**, provide:

1. **Source Salesforce Org** – The org to retrieve metadata from.
2. **Package Type** – How ARM gathers metadata:

   * **Unpackaged Mode:** Retrieves metadata modified since the last ARM cycle (or since **Start Date**, if set).
   * **Unmanaged Packages:** Provides editable building blocks installed as application templates.
   * **Managed Packages:** Used by partners to distribute applications created in a **Developer Edition** org.

   For more information, see the [Salesforce help article](https://help.salesforce.com/HTViewHelpDoc?id=sharing_apps.htm\&language=en_US).

**Additional Options in the Build Section**

<figure><img src="/files/lEwdCaZ8sqUCraueqIfH" alt="Additional build options"><figcaption><p>Additional Build Options</p></figcaption></figure>

1. **Auto Switch to Bulk Retrieve Service if Job Hits Metadata Governor Limit:** Use batch retrieval when a job approaches the 10,000-file or 39-MB limit. Specify **Batch Size** (up to 10,000).
2. **Exclude Installed (Managed) Components and Changes:** Skip all managed-package components.
   * **Exclude All Manually Created Components:** Also skip custom components in managed packages.
3. **Incremental Build:** Fetch only metadata changed since the previous successful deployment, improving build time.
4. **Include Picklist Modifications:** Always include picklist fields, even if the “last modified” date is unchanged (source = Salesforce org only).
5. **Prepare Destructive Changes:** Delete unwanted metadata in the destination org before deployment.
6. **Generate Code Coverage Report:** Include Apex test-coverage details.
7. **Run Static Analysis Report:** Identify code-quality issues before production.

   <figure><img src="/files/CaI5s2XTJm5RQ8zv441L" alt="Static analysis options"><figcaption><p>Static Analysis Options</p></figcaption></figure>

   * **Apex PMD / Checkmarx:** Set scan criteria and **Priority**. If the threshold is not met, the build is marked unstable.

     <figure><img src="/files/2cQ1izAW0tWEBpGAo393" alt="Criteria for Apex PMD and Checkmarx"><figcaption><p>Criteria for Apex PMD and Checkmarx</p></figcaption></figure>
   * **CodeScan / SonarQube:** Choose to scan all metadata or only newly added components, then set a **Priority**.
     * **Run on All Supported Metadata Types:** Scan every retrieved component.
     * **Run on Newly Added Supported Metadata Types:** Scan only newly added components.

       <figure><img src="/files/BfxtzK84AO96ileCveWx" alt="Scope options for supported metadata types"><figcaption><p>Scope Options for Supported Metadata Types</p></figcaption></figure>

   *For more information on running **Static Code Analysis in CI Jobs**, see* [*this guide*](/product-guides/arm/arm-administration/static-code-analysis-in-ci-cd.md)*.*
8. **Additional Profile Packaging Options:**
   * **Remove Login IP Ranges:** Omit IP-range restrictions from profiles.
   * **Remove System and User Permissions:** Omit profile permissions from deployment.
   * **Exclude Metadata Types:** Skip metadata you don’t need in the build.

{% hint style="info" %}
**Important Note:** To set exclusions globally, open **My Account > My Salesforce Settings**, choose **Exclude metadata types**, and select the types to skip. These settings apply to all future CI jobs.
{% endhint %}

#### Deploy <a href="#deploy" id="deploy"></a>

Deploy or validate the package in a destination org:

<figure><img src="/files/ta3d4bEE3msPGvIa3Fmj" alt="Deployment options"><figcaption><p>Deployment Options</p></figcaption></figure>

* **Deployment Org:** Select the destination org.
* **Apex Test Level:** Choose the test scope:

  <figure><img src="/files/7zLkpBL6exvF3zupx05h" alt="Apex test level options"><figcaption><p>Apex Test Level Options</p></figcaption></figure>

  1. **Use Salesforce Defaults** – Default Salesforce behavior.
  2. **No Test Run** – No tests unless deploying to production.
  3. **Run Specified Tests** – Run only named tests; ARM checks coverage per class (75 % minimum).
  4. **Run Local Tests** – Run all tests except those from managed packages.
  5. **Run All Tests in Org** – Run every test, including managed-package tests.
  6. **Run Tests Based on Changes** – Identify and run relevant test classes; optionally update the default test-class list.

{% hint style="info" %}
**Important Notes:**

* Specify test class names comma-separated in **runTests** when **Run Specified Tests** is selected.
* Ensure tests have run at least once before using **Run Tests Based on Changes**.
  {% endhint %}

**Additional Deployment Options**

<figure><img src="/files/9nzjHflnHZt81ZuJOhr8" alt="Additional deployment options"><figcaption><p>Additional Deployment Options</p></figcaption></figure>

1. **Validate Only:** Run validation without deploying.
   * **Prevent Deployment:** Disable deployment for validation-only jobs.

{% hint style="info" %}
**Important Note:** Test cases do not run when **Validate Only** is selected.
{% endhint %}

2. **Rollback:** Save a backup to allow rollback.
3. **Ignore Missing Visibility Settings if Package Contains Profiles or Permission Sets:** Deploy profiles/permission sets even if visibility settings differ.
4. **Ignore Installed (Managed) Components:** Skip managed-package components.
   * **Ignore All Manually Created Components:** Also skip custom managed-package components.
5. **Ignore Warnings:** Deploy even if warnings occur.
6. **Do Not Include 'Skip Members' During Deployment:** Override global skip settings for this deployment.
7. **Run Destructive Changes:** Choose pre- or post-destructive changes.
8. **Apply Search and Substitute Rules:** Apply custom find/replace rules during deployment.
9. **On Successful Deployment:** Trigger post-deployment actions (Skuid pages, CI jobs, environment templates, DataLoader processes, merge processes, Jenkins jobs, parallel processors, or a sequence of activities).

   <figure><img src="/files/zNmLsI3W1y9t4LshbQK7" alt="Post-deployment actions"><figcaption><p>Post-Deployment Actions</p></figcaption></figure>

   *You can sequence multiple post-deployment actions:*

   <figure><img src="/files/G7WkA34IpwuPAKL1e7cc" alt="Set sequence for post activities"><figcaption><p>Set Sequence for Post Activities</p></figcaption></figure>

   <figure><img src="/files/ECCECg2vT5xMLSpEWahv" alt="Sequential workflow example"><figcaption><p>Sequential Workflow Example</p></figcaption></figure>

#### Dependency Analyzer <a href="#dependency-analyzer" id="dependency-analyzer"></a>

Analyze metadata dependencies to avoid breaking changes:

<figure><img src="/files/vdkDC3oXboNYlFsjjyLX" alt="Dependency Analyzer"><figcaption><p>Dependency Analyzer</p></figcaption></figure>

#### Tests <a href="#tests" id="tests"></a>

Run functional tests before deployment:

<figure><img src="/files/Kxx54kvl9toobeOAnDp0" alt="" width="375"><figcaption></figcaption></figure>

* **Version Control:** Choose repository, branch, and test type (Selenium Maven, Selenium Non-Maven).

  <figure><img src="/files/RlywvKuPn5sg8LQtuFZL" alt="Version-control test options"><figcaption><p>Version-Control Test Options</p></figcaption></figure>
* **AccelQ:** Enter **Project Name**, **Test Job Name**, and parameters.

  <figure><img src="/files/Ib9YcjaXSG0WRGsqnz0R" alt="AccelQ test settings"><figcaption><p>AccelQ Test Settings</p></figcaption></figure>
* **Provar:** Provide repository, branch, test-case root path, and execution path.

  <figure><img src="/files/KAiQUZg93dwG3j41dahf" alt="Provar test settings"><figcaption><p>Provar Test Settings</p></figcaption></figure>

#### Callout URL <a href="#callout-url" id="callout-url"></a>

Configure HTTP callouts to external services. See the [Callout URL guide](/product-guides/arm/arm-features/automation-and-ci/configure-callout-url.md).

#### Notifications <a href="#notifications" id="notifications"></a>

Send success or failure emails to selected recipients.

<figure><img src="/files/oqm6Gvx1tLzHfazCLmab" alt="Notification settings"><figcaption><p>Notification Settings</p></figcaption></figure>

#### Schedule <a href="#schedule" id="schedule"></a>

* **Daily** – Run every day at the chosen time or interval.
* **Weekly** – Run on selected day(s) and time.
* **No Schedule** – Save the job and trigger it manually.

#### Save

Click **Save** to store the CI job settings.

If you deploy compiled **FlexCard** and **OmniScript** objects, verify both:

<figure><img src="/files/A7jaA2hvH7LPschdAvI7" alt="Vlocity compilation settings"><figcaption><p>Vlocity Compilation Settings</p></figcaption></figure>

1. The destination org is registered via **OAuth** (not Standard).
2. **Local Compilation** is enabled in **My Account** and the correct **Access Key** is entered.

For credential-usage details across CI job types, see the [FAQ](/product-guides/arm/troubleshoot/arm-faqs/ci-jobs.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-features/automation-and-ci/create-a-new-ci-job/deploy-a-package-from-a-salesforce-org.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.