August 7, 2017

A Powerful “Early Warning” System for Salesforce Developers with AutoRABIT and Perforce

Partner
Thumbnail

Niranjan Gattupalli – Sr. Director of Customer Success

Salesforce has become omnipresent across industries for customer relationship management, which can be customized to a company’s individual requirements for a 360-degree view of its customers. The increasing demand for Salesforce has brought in the need for more sophisticated functionalities for developers to create and deploy applications faster with higher quality to meet the business expectations.

AutoRABIT is an end-to-end continuous delivery and release management suite for Salesforce applications with unique capabilities for version control, metadata deployments, Continuous Integration (CI), data migration, and test automation.

The Perforce Helix Development platform, with Version Control System (VCS) and Application Lifecycle Management (ALM) integration built-in, has been a great choice for development teams with design needs surrounding compliance and stability.

Here are the major challenges of Salesforce teams while trying to achieve CI with version control:

  • Lack of knowledge about using version control along with best practices for the teams coming from a “point-and-click” environment like Salesforce.
  • Delayed releases due to deployment failures caused by missing dependencies as well as code coverage issues.
  • Salesforce complex metadata structure that causes issues with profiles and custom labels.

 

How do Salesforce developers benefit with AutoRABIT and Helix together?

The Helix development platform has been a preferred choice for developers with some unique offerings in the space of version control and ALM as listed below:

  • Integrated ALM

Control, visibility, and traceability of the entire development process

  • Fast and Scalable, Everywhere

Federated architecture supports thousands of global users and millions of daily transactions

  • Single Source of Truth

One repository contains contributions from all teams and all artifacts from planning process

  • Security and Compliance

Granular permissions; end-to-end visibility; auditability and traceability.

 

AutoRABIT Check-in Editor for Helix VCS

AutoRABIT has a powerful check-in editor which is unique for Salesforce developers to check in code/configurations to Helix VCS repos effortlessly. The key features of check-in editor include:

  • Ability to understand Salesforce metadata: The editor understands the Salesforce metadata structure, can fetch the changes done by a user (up to the child metadata level) along with dependencies, and the developer can push the changes to Helix VCS. For example, a user modifies a custom field, AutoRABIT allows the user to only check in the custom field irrespective of other changes done in the custom object in the Sandbox.
  • Smart Profile Check-ins:Checking in code to VCS from the Force.com integrated development environment (IDE) would commit the entire profile to version control pushing several unwanted permissions modified in the Org causing inconsistencies when the profiles are deployed to other environments.

    It is the reason why 60-70 percent of even matured Salesforce teams who use version control and CI still do not favor including profiles into version control and CI deployments. With AutoRABIT checking in a profile along with other metadata will ensure only the permissions of respective metadata are checked in.

  • Tag Check-ins to Helix ALM work items: The developer can check in changes to Helix VCS by associating the check-ins to Helix ALM work items so that there is higher degree of traceability and collaboration for the work items.

 

AutoRABIT Check-in gate for Helix VCS

AutoRABIT has a powerful check-in gate that ensures developers check in only high-quality code to Helix VCS. It offers two features that can be utilized to confirm whether the code quality is maintained:

  • Validation reports for the check-in:With AutoRABIT check-in gate, Salesforce developers can verify if the code is deployable, the code has not introduced any new coding violations and is meeting the code-coverage benchmarks before checking-in the code.
  • Approval process: The extensive validation reports will be notified to the reviewer. Based on whether the approver can approve or reject the check-in, the developer can push the changes to version control.

 

“No Deployment strategy” for Helix ALM work items

AutoRABIT has powerful deployment capabilities that let you deploy metadata changes from either version control repos or from a Salesforce Sandbox to a destination Salesforce environment.

With AutoRABIT, a developer can deploy changes from Helix VCS repos into Salesforce based on Helix ALM work item status.

For example, an AutoRABIT CI job can continuously deploy all the Helix ALM work items which are in “ready for QA” status into QA environment.

It is effectively a “No Deployment for Release Managers” since AutoRABIT can track the user story/work item status and deploy the changes automatically into Salesforce environments based on the workflows defined in Helix ALM.

With its powerful check-in editor, which reduces the complexity of code check-ins to version control as well as continuous validation of check-ins, AutoRABIT and Helix product development ensure great quality of code and reduced deployment failures to accelerate developer productivity and release velocity.

 

Conclusion

AutoRABIT check-in gate for Helix serving as an “early warning” system enables Salesforce developers to check-in quality code that meets enterprise coding standards. With a powerful deployment module in AutoRABIT that deploys code changes from Helix VCS, either from a stream or from a Helix ALM work item, Salesforce release management teams can experience continuous delivery of their applications.