Deploy your features or fixes conveniently directly from Hutte to the target org of your choice.

While your team may use the Hutte Release Module or CI/CD pipelines for automating deployments from your Git “source of truth”, 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 on a “per feature” basis.

https://hutte.intercom-attachments-7.com/i/o/774848139/214749c5ca928009aa244743/pKIJm7gdb1dSCxOli_JbM9bhmsH0EHX1s1REWtevqkDjirysAj77Sn6WjneyA1OgZNPepy7dsFqBWQ80SIOXkM3J90SJRA4QSgmygPQCIgR2boQdBi1dHo2J_x7X4P5MTzBOduAvUG_6gxcfja-QOtw?expires=1724861700&signature=43e6c1c406d132a25c074d634992dd49b97575ae568b6ddd8244100c72a8114a&req=cycjHs12nIJWFb4f3HP0gCQf0uX6pzP2LFYBV5EIqYdyBendbopPSN3aqnUx CbRewt9APFGyvCM2gQ%3D%3D

https://hutte.intercom-attachments-7.com/i/o/774848150/b1f51d8c6ab46c79ddce5423/37SbCBklHcCvdaYajIah5zRz0vva1F-Qe5dlQJSamu3C1t0mjJTCAcvaPzOCDN8S0Sq2LGR55nymIUuQ7omFxCYdbuzUI1EjSgED-HlqckgctpzYsouFAtFNtFKlhU7PU1zGAFaBKKAv4DBDKK_JqH0?expires=1724861700&signature=36132f5c96c75b0a766f9afdac477b6b6cc63aef934251668dd384034b3f9a7f&req=cycjHs12nIRfFb4f3HP0gClqH5SvfqZVkFKARn8oajw%2FR7JY0Tq3W1BFQlwN 5xs2%2Btm%2FaYEYULuieQ%3D%3D

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.

https://hutte.intercom-attachments-7.com/i/o/774848154/d0ef6809ccdb6db77ad94215/1-R4vbI67pTdU8QLyKFoZCVQ5K3b69os38Xw4MeZEoHiT4ZLD-Ax29zmcY99xXYuX4eOkgJ11TAZc4z6dRPO60ZklXQEjIX0Wp6qhNafTWi8yo9SwOQiw81_u2v_PPKyRgVFSSJ6EoQ3wmae-FPzVuo?expires=1724861700&signature=4f359aed8125ddc78f702d7a47f151f7255644b6685ccd4960d0a5ce5913cbfd&req=cycjHs12nIRbFb4f3HP0gHq7n93lFtlZl4X%2F%2FRXh0IEcOUeUSseqsgZkS2KL XGoyzDlLRXzgtcvrUA%3D%3D

https://hutte.intercom-attachments-7.com/i/o/774848160/61985713f37fc345bae538fd/QiQMDnv4IxHP8rQCC4n4_JHkZkWmifBa3XU8gT9D2dO4LdHutjBjJd4xLODLOtWyDGvyM9_SAJP0FzLBv4LidAw2wo-lxFgC1kcBOX8WwUGqvCf5Ag7l5lNBU1Rlca3oe29Zp6pkaZ6UlFZskMCLqyo?expires=1724861700&signature=00d423c88aaccf628cf88f0593aec321a356059278e42185a657eca78c35c46c&req=cycjHs12nIdfFb4f3HP0gCBs1MgAw3vf2KrsDcimcSsh5uo5C%2FLANuTD44ml 7S71doIAuzCD9v1T5g%3D%3D

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.

Deployments require users to have deploy permissions on the respective Target Org.