Description
Gearset has acquired Clayton! This video demonstrates how Gearset and Clayton integrate in a typical workflow. Clayton provides best-in-class static analysis for Salesforce code and configuration, helping you catch and fix issues earlier in the development cycle. Bringing this functionality onto Gearset’s DevOps platform will help Salesforce teams to embed code analysis into their DevOps lifecycle and deliver high quality, bug free, and secure code at speed. Find out more here: https://gearset.com/solutions/code-analysis/
Transcript
Like many admins and developers working on the Salesforce platform, my role is to deliver high quality, bug free, and secure code to the business at speed. Gear set helps me quickly and efficiently bundle changes into a deployment, but until now, did very little to ensure the quality of those releases.
Clayton helps me to optimize my Salesforce release process and achieve greater DevOps maturity by catching bugs and vulnerabilities earlier in the process, preventing issues making it into the application.
We can see here that I've just opened a pull request within my gear set pipeline.
When opened, the Clayton scan will run and results are presented as status checks. As a developer, I'm hugely relieved that Clayton has detected a potential security vulnerability and has blocked my non compliant code from being promoted.
Within Clayton, I can see my insecure code.
And Clayton auto fix will automatically suggest a remediation for this violation, reducing the need for manual intervention and drastically streamlining the time to resolution.
Once my auto fix is generated, I can then simply open a pull request of these suggested changes, which can then be merged back into my feature branch from within my gearset pipeline.
So let's go over then to gearset and do this together.
On the left hand side, I can see my auto fix as shown here. I can simply apply these fixes, which will do the merge in git, and then my status checks will rerun on my original pull request.
So now I can still see that original pull request I opened. The Clayton scanner's rerun, ensuring that my changes are now secure.
This is then available to be promoted, so I can simply select this pull request and use Gearset to promote this change.
So in summary, by integrating Klaytn with Gearset, code reviews become woven into the overall release management experience.
This provides an integrated and unified release process encompassing streamlined developments and faster code reviews, and now allowing engineering teams to spend more time building and less time fixing, as well as automation, testing, and analysis with the ability to define a consistent coding standard across development teams.
To find out more, please get in touch or start a free trial via gearset dot com.
