Atlas builds ingenious solution using Vlocity and Gearset
Two years ago, Atlas adopted Salesforce and began building out cloud-based services for new and existing customers. The insurance company wanted to capitalize on the offering from Vlocity (Salesforce Industries), as Malcolm Camilleri, Senior Software Engineer, explained:
The Atlas developers have been building a customer portal that’s easily accessible to customers on the Atlas site while also being connected to Salesforce. The team has managed this by exporting a Lightning Web OmniScript from Salesforce and hosting it as an application on Heroku.
Developing this portal is a fascinating use case for Vlocity. And making the project a success has seen the Atlas team adopt Gearset to support their implementation and establish an efficient release process.
Gearset ticks all the boxes
The Atlas developers needed to find a tool that would help them manage deployments and releases of their development work building the customer portal. Since Vlocity DataPacks are distinct from Salesforce metadata, the team needed a solution that could handle Vlocity deployments specifically.
The Salesforce product team recommended Vlocity DX for the job. But this didn’t do the trick.
Malcolm set out to find an alternative, and was looking for deployment tooling that included rollback functionality, since it’s
important to have in your back pocket. This led Malcolm to Gearset, and he was immediately struck by how easy it was to use.
Not only did the Atlas team all find deploying with Gearset intuitive, they soon discovered the power of Gearset’s continuous integration (CI) as well. Malcolm worked closely with Tom Smith, one of Gearset’s Development Team Leads, to set up a CI process that suited the team’s workflow.
80% less time spent on deployments and releases
Deployments of Vlocity DataPacks are now significantly faster for Malcolm and his team. As well as being intuitive, Gearset brings everything together in one place for better visibility and control.
The Atlas team has a release pipeline made up of various environments, and also maintains two repositories in Bitbucket. One particular pain point before Gearset was merging changes from one repository to the other, which used to be a manual process. Now, a CI job in Gearset enables the team to deploy changes from one repo to a branch of the other repo at the click of a button.
Gearset makes a huge difference
Looking to the future, Malcolm hopes to see Atlas using Gearset to manage even more of the team’s DevOps process, and has been keeping an eye on the development of Gearset’s Pipelines offering.
Our plan is to use Bitbucket just as a code repository and run everything through Gearset, Malcolm says, citing the much higher success rates for merging changes within Gearset.
Malcolm is clear that he would recommend Gearset to any team for Vlocity deployments, especially as part of a mature DevOps process.