Anonymous
My feedback
5 results found
-
16 votes5 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Anonymous
supported this idea
·
An error occurred while saving the comment -
7 votesAnonymous
supported this idea
·
-
6 votesAnonymous
supported this idea
·
-
2 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Anonymous
supported this idea
·
-
107 votes
Hello. A large number of commenters requested the ability to carry out value replacements as part of metadata deployments.
Gearset now offers a feature called Environment Variables that lets you do just that!
It works with both manual and CI deployments and lets you target either a Salesforce org or a Git repo of your choice. And, for a number of key metadata types, you can even specify the exact 'field' where the replacement should take place.
If you have any feedback on the Environment Variables feature, please open a new feature request or simply let us know in the in-app chat.
Thank you for upvoting this feature request and we hope that you will find the Environment Variables feature useful.
Blog post: https://gearset.com/blog/environment-variables/
Support doc: https://docs.gearset.com/en/articles/5557015-using-environment-variables-in-gearset
Anonymous
supported this idea
·
We have similar issue. We have a bigger team and many developers are keep on changing the managed package custom objects. CI jobs is excluding these changes in every deployment which makes us to deploy manually. Manual deployment adds work effort and time consuming. If there s way that Gearset automatically skips the suggestions " exclude managed package changes" and keep the changes that would be greatful.