Andres Fernandez de Prado
My feedback
7 results found
-
37 votes
We're currently reviewing how we can facilitate deployments to multiple Salesforce instances simultaneously. Please let us know how you manage this currently, or how you would like to manage it - thanks!
An error occurred while saving the comment -
1 voteAndres Fernandez de Prado
shared this idea
·
-
3 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Andres Fernandez de Prado
supported this idea
·
-
3 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Andres Fernandez de Prado
supported this idea
·
-
4 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Andres Fernandez de Prado
supported this idea
·
-
10 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Andres Fernandez de Prado
supported this idea
·
-
9 votes
An error occurred while saving the comment Andres Fernandez de Prado
commented
This should include the validation errors detected by Gearset itself, and not just the SF Validation errors.
Andres Fernandez de Prado
supported this idea
·
Pre- and post-deployment steps in our pipeline often involve manual deployment of components not managed through the pipeline. We currently use the 'Deploy to new target' button on the Deployment Results page to do the deployment to all the developer sandboxes.
It would be great if 'Deploy to new target' supported specifying multiple destinations at once. This would be a good place to have this functionality, as the starting point is a deployment that already succeeded, albeit in a different org. In our experience, if the first deployment succeeded, all deployments to other orgs succeed as well.