Martin Novacek
My feedback
16 results found
-
27 votes
An error occurred while saving the comment Martin Novacek supported this idea · -
30 votesMartin Novacek 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
Martin Novacek supported this idea · -
9 votesMartin Novacek supported this idea ·
-
11 votesMartin Novacek supported this idea ·
-
6 votesMartin Novacek supported this idea ·
-
9 votesMartin Novacek supported this idea ·
-
9 votesMartin Novacek supported this idea ·
-
7 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Martin Novacek supported this idea ·
-
2 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Martin Novacek supported this idea ·
-
14 votesMartin Novacek supported this idea ·
-
12 votesMartin Novacek supported this idea ·
-
4 votesMartin Novacek supported this idea ·
-
21 votes2 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Martin Novacek supported this idea ·
-
2 votesMartin Novacek supported this idea ·
-
8 votesMartin Novacek supported this idea ·
Specially needed if you push a change in the repository and this will be interpreted as a deletion and the CI job deploy only changes and new things.