Nikita Belov
My feedback
15 results found
-
12 votesNikita Belov supported this idea ·
-
30 votesNikita Belov supported this idea ·
-
3 votesNikita Belov shared this idea ·
-
3 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Nikita Belov supported this idea ·
-
3 votesNikita Belov supported this idea ·
-
5 votesNikita Belov supported this idea ·
-
7 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Nikita Belov supported this idea ·
-
11 votes
An error occurred while saving the comment Nikita Belov supported this idea · -
to add an option to not to run unit tests validation in CI job in case there are no changes detected
2 votesNikita Belov shared this idea · -
14 votesNikita Belov supported this idea ·
-
27 votesNikita Belov supported this idea ·
-
41 votesNikita Belov 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
Nikita Belov supported this idea · -
1 voteNikita Belov shared this idea ·
-
1 voteNikita Belov shared this idea ·
Very needed