Paul Mackintosh

My feedback

  1. 99 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    19 comments  ·  Help us improve Gearset » New feature  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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  

    An error occurred while saving the comment
    Paul Mackintosh commented  · 

    In order to support a development pipeline (e.g. Dev Environment -> Staging Environment -> Production) allow Metadata from the source Org to be modified before deployment to the target Org.

    e.g. I have a RemoteSiteSetting in source that points at https://dev.example.com and in my staging environment I need this to point to https://stg.example.com

    Paul Mackintosh supported this idea  · 

Feedback and Knowledge Base