# 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](https://knowledgebase.autorabit.com/product-guides/troubleshoot/known-issues-limitations/salesforce-known-limitations#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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FMkx80OPOmvwaW1XJ4TS4%2Fimage.png?alt=media&#x26;token=4fa45b64-d591-4604-9eee-3e009a936788" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FFcrO3zt9VXydQ03EecJv%2Fimage.png?alt=media&#x26;token=daa59f50-ed29-4aae-82b4-8608a5ad1e43" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FLao4xR5EwnlFYfIEsc5I%2Fimage.png?alt=media&#x26;token=58032beb-1ce3-4fb5-8f2f-0679c0100de4" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F7ybFuTvI164IDMrQRhGG%2Fimage.png?alt=media&#x26;token=a61e7174-2774-4d8d-ae7a-48d20c0305c2" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FhwmkqRHdVjPQhyRwEr27%2Fimage.png?alt=media&#x26;token=d430edf8-c5d9-49f8-931e-9ad5cf7cab3e" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FZEckiQlS50Io4kmJ5gTO%2Fimage.png?alt=media&#x26;token=3cda86c4-9866-454d-918f-0f46aea05f5a" 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*](https://knowledgebase.autorabit.com/product-guides/arm/arm-administration/static-code-analysis-in-ci-cd)*.*
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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fve2vqTxHQLe4rhkmz4Wn%2Fimage.png?alt=media&#x26;token=c2e33b2a-be1a-4b83-b954-d208e66343c5" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FwphwOrTKGWZmtSM35AZa%2Fimage.png?alt=media&#x26;token=9eae8c4f-9ae2-4d58-b713-e6545e67a043" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F7bJBgbMGA2Ou4VhX3tGs%2Fimage.png?alt=media&#x26;token=57caf968-a143-4b97-a5a1-3a1deea7e56a" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FgX0O0Ssq3Mck0KRnmqR8%2Fimage.png?alt=media&#x26;token=816dcaf0-969f-4ad4-9e4f-eabac86f4c5a" alt="Post-deployment actions"><figcaption><p>Post-Deployment Actions</p></figcaption></figure>

   *You can sequence multiple post-deployment actions:*

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FYB125mKCx2yn3FHQ4ems%2Fimage.png?alt=media&#x26;token=3b6ab12f-3ed3-44fd-8a4d-c44364d4cbde" alt="Set sequence for post activities"><figcaption><p>Set Sequence for Post Activities</p></figcaption></figure>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fy7frJC0mBnhWWaiXmjgT%2Fimage.png?alt=media&#x26;token=99e71e9e-20a2-40b3-9254-6f7edf7f4088" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fk2zxJ8XSS9tskyN2QXaM%2Fimage.png?alt=media&#x26;token=c13437be-0ae9-4204-a0c7-fb9af85df04a" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F3PuligR5b67XsG1HNeKV%2Fimage.png?alt=media&#x26;token=20f7392b-96d9-4edc-9ef6-2284e07f5750" alt="" width="375"><figcaption></figcaption></figure>

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

  <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F65wgGBxcE2F2Y4afI97y%2Fimage.png?alt=media&#x26;token=6e00320d-fc19-46d6-b5ae-d7ad854465a7" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FxEl7ljPE6RN7fHbAx3Xs%2Fimage.png?alt=media&#x26;token=128b70d1-9ca0-4ec0-93c8-bcbe893d5024" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F90AtaJjbKGOKWCsK0iwC%2Fimage.png?alt=media&#x26;token=b68cafb4-fde6-430d-a7ba-f4d24c6e234d" 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](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/automation-and-ci/configure-callout-url).

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

Send success or failure emails to selected recipients.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FJPJ9h9BmO0fTjFtgCTW8%2Fimage.png?alt=media&#x26;token=78619a43-2fd3-40e7-a287-bdb47951b2f8" 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="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fw2mnvrX0fiStLGAFi7RF%2Fimage.png?alt=media&#x26;token=3684a5a6-f2bb-4c87-a352-48df9efb637c" 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](https://knowledgebase.autorabit.com/product-guides/arm/troubleshoot/arm-faqs/ci-jobs).