Force.com

Feature SalesForce

CI Classes

1. SFRepository: Git repository synchronized with SalesForce development sandbox

2. Attributes

   • Repository path: The path in the Clarive server where the Git bare repository will be located
   • Relative path: The relative path that will be prepended to the object path in both job items list and in the checkout dir for objects from this repository
   • Revision mode: Working mode of the repository in jobs when checking out and regression management. If Diff with environment is selected, Clarive will control that the revision to be installed won't cause any regression by checking that there is common history between the commits to be installed and the version installed in the environment
   • Tags mode: The mode that Clarive will use to tag the repository after a job deployment

3. SFRevision: (Internal) One revision will be created when any commit is attached to a changeset.

4. SFInstance: Defines the different SalesForce instances that will be target of deployment jobs

5. Attributes
   • User: email of the user that will connect to the SalesForce instance
   • Password: password + token of the user needed to connect to the SalesForce instance
   • API Version: Version of the API used to deploy APEX objects to this instance

Palette operations

1. Execute Force.com task: Executes the goal selected in the configuration (testDeploy, deployCode or undeployCode) in the selected instance using the code found in the path selected in the configuration
2. Generate package.xml file: Generates the package.xml file needed to deploy the code found in the path specified in the configuration to the instance also selected in the configuration