While your team may use CI/CD pipelines for automating deployments from your Git host, there are situations where you might want to move the changes performed in a development environment – no matter if it’s a Scratch Org or Sandbox – to a different org.
Hutte supports connecting multiple Salesforce orgs as deployment targets for each project. When working on a change request, bug fix, or feature in a Sandbox or Scratch Org through Hutte, you're able to deploy the source you have been working on to a target org of your choice.
Additionally, you are able to specify if you want to run a full or validation deployment and to set details of the test execution during your deployment. If a deployment fails, you can click on the red box to open a deep-link to a detailed “Deployment Status” page, where you can investigate the reasons why the deployment failed (e.g. a lack of test coverage, etc.).
Easily select test classes to run during your deployment
You might have found Salesforce's change set UI frustrating, as it requires you to type class names for tests during deployments. However, with Hutte's deployment functionality, you can conveniently select the test classes to run from a list in your deployment target organization.
Are you getting started with your CI/CD on Salesforce? We have a recipe for that!