Build a Package from Salesforce

Overview

Create a package from a Salesforce org based on a Start date and deploy or validate that package in a different Salesforce org. You can also configure the job to run functional test cases stored in version control.

Procedure

1. Log in to ARM.

2. From the top navigation bar, select Create New > New CI Job.

   
3. Click the Package from Salesforce tile.

   
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 has several sections explained below.

Build

Under Build, provide:

1. Source Salesforce org – The org to package.

2. Package type – How ARM gathers metadata:

   • Unpackaged mode – Retrieves metadata changed since the last ARM cycle (or since Start date, if set).

   • Unmanaged package – Retrieves components from an unmanaged package so you can edit them.

   • Managed package – Retrieves components from a managed package created in a partner dev org.

   

Additional build options

1. Auto switch to bulk retrieve service if job hits metadata governor limit – Automatically uses batch retrieval when a job approaches Salesforce limits. Specify Batch size (up to 10 000 items).

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. Include picklist modifications – Always include picklist fields, even if Salesforce did not update the “last modified” date (source = Salesforce org only).

4. Generate code coverage report – Include Apex test-coverage details.

5. Run static analysis report – Run an SCA tool before the build proceeds.

   • Apex PMD / Salesforce Scanner – Choose whether to scan all Apex classes or only those modified after a given date, and set a Priority threshold.

     
   • CodeScan / SonarQube – Choose to scan all supported metadata types or only newly added ones, and set a Priority threshold.

     

     • Run on all supported metadata types – Scan every retrieved component.

     • Run on newly added supported metadata types – Scan only components added in the current retrieval.

       

   For details on running static code analysis in CI jobs, see this guide.

6. Additional profile packaging options

   • Remove login IP ranges – Omit IP-range settings from profiles.

   • Remove system and user permissions – Omit profile permissions from deployment.

7. Exclude metadata types – Globally omit specific metadata types from all CI jobs.

Notifications

Send success or failure emails to selected recipients.

Schedule

Run the job automatically:

• Daily – Run every day at the chosen time or interval.

• Weekly – Run on selected day(s) and time.

• No schedule – Save the job and run it manually when needed.

For credential-usage details across CI job types, see the FAQ.

What next?

After saving the job, ARM redirects you to the CI job results page, where you can start the first build.

What next?

After saving the job, ARM redirects you to the CI job results page, where you can start the first build.