Sometimes during a complicated deployment I need to try a few different strategies to get things to work. For example, I may need to just send up one piece or set of metadata up first.

The problem is, each time I do this, I have to wait for problem analysis to complete, which takes a couple minutes. Normally during a deployment I do want problem analysis to run, but if I want to quickly send up a single object, I have to wait a few minutes while Problem Analysis runs, and the time waiting adds up.

Maybe a quick deployment option from the compare screen, where i could select my tests and either validate or deploy what's currently checked?

Thanks!

I simply want to be able to add some lines of text to the emails that are triggered.

In our case this would simply be to let the team know the deployment was complete please proceed with any manual steps for example. In our org this would simply save a step for the release manager to have to trigger an email stating this and be included in the email triggered by gearset.

This functionality might also play out nicely that we could have some more specific text around the test jobs that we trigger. For example, we have thought to send these results to our change advisory board and some custom text within this would be handy as well.

This is a common error received during deployments:

Error: Metric, gauge, or table dashboard component missing indicatorLowColor attribute (line 70, column 33)

This is a suggestion to Gearset team for there feature Deployment analysis if they would pick this error in advance before deployment.

Observation: This issue occurs when the Dashboard is created in Lightning. (I cannot confirm though)

Resolution:

Downloaded package.xml and component

Basically, after I pulled the dashboard metadata from source org, I opened it and found the
<componentType>Table</componentType> tag, and right under it I added this:

<indicatorHighColor>#00716B</indicatorHighColor>
<indicatorMiddleColor>#ffb75d</indicatorMiddleColor>
<indicatorLowColor>#C23934</indicatorLowColor>

After this change I managed to deploy everything to my destination org, and everything seems to be working fine.

Hope this helps.

Thanks.

A common use case is:
1. Compare default(66) source and target
2. Select some files
3. Deploy
4. Get some error indicative of either missing file or out-of-date file(s)
5. Fix file(s) in underlying org/source branch.
6. "Back to results" Optionally mark additional files as selected.
7. "Refresh Comparison"

This takes too long, you just want the selected files to compare (and really, just get on with deploying). You don't want to wait for both source and target metadata to load and compare. You don't want to uncheck/check specific metadata components that represent your selected files. You just want a refreshed set of selected files from the last compare

VSTS offers the ability to create build definitions to validate/deploy your code, but Gearset customers don't have much options natively in VSTS to trigger a Gearset deployment. We can scan a code repository for changes every 4 hours in order to do a CI deployment-- but that's about it.

VSTS offers the ability for vendors to create "Build Tasks" for their applications, where you can initiate a VSTS build and get results. This is basically a controlled version of API access to the tool.

More information:
VSTS Marketplace - https://marketplace.visualstudio.com/vsts
VSTS "Add a Build Task" - https://www.visualstudio.com/en-us/docs/integrate/extensions/develop/add-build-task

It would be so great to be able to intiate a Gearset deployment directly from within VSTS, so we could easily integrate Gearset within our company's workflow.

Our other alternatives are embedded Ant using the Force.com Migration Tool (ugh) or competitive vendors to Gearset such as Blue Canvas-- neither of these are attractive options for us, so we'd love if Gearset offered this!