Currently when a PR Validation fails (Deploy CI Job with Validate Target setting turned on), the user can click the Gearset "Details" link to go into Gearset to see the exact error.

Many of our devs use VS Code and Github for their daily work and only rely on Gearset for the CI job. Having them jump into Gearset just to see the error is time consuming and not very intuitive for them. Sure we can find the same errors within the target org of the CI, but at that point the list of validations is large and it's hard to find.

If we could have the CI job trigger a comment on the PR of the Success or Failure (with errors or at least first 10 errors) then our developers could have a smoother time staying within Github.

Would like to see the ability to set the IgnoreWarnings as an override for an individual Compare and deploy, in addition to at the global level. Occasionally, we will do a community deploy, for example, that returns a warning about a page that includes a Dashboard component, with the warning that the Dashboard ID or the Filter ID might not exist in the target environment. Once we see those errors in the validation results, it would be convenient to rerun the deploy, and ignore those warnings. Possibly similar to how the Test execution options are set on the Deploy button dropdown menu.

I had unit testing jobs running ALL tests in source (full sandbox) and target (production) org - resulting in 80% and 79% test coverage. However, when I started to deploy my changes - the validation failed because test coverage was only 74%. Finally, after a few days, I figured it out.

I was just simply clicking "Validate" (i.e., did not choose specific tests). In the past - that ran "all tests". But something seems to have changed. When I picked "choose tests", about half the tests in my org were "automatically selected". I manually selected all other tests - effectively forcing all tests to run. This time the validation passed!

It would be great if there was some output from Gearset during the validation in terms of what tests were being run (partial vs all)

Hi All,

We are looking for a SCA feature so that instead of showing all the errors and warning in the whole file while doing compare or deploy, It Should only show the SCA errors and warning for the last commit or for commits during an specific time interval.

For Example I have an existing Apex class which is having 1000 lines of code and say 100 errors are there as per GS SCA analysis. Now let’s assume I am working on that file for my current sprint and I am adding another 100 lines of code in that class. Now after doing the compare and deploy the SCA should give me the errors and warning for the latest 100 lines of code and not for the complete file.

Regards
Shahnawaz

When I choose to compare metadata with my source as my VCS, there was an "&" char in the recordtype XML definition file.

    <values>
        <fullName>Food & Beverage</fullName>
        <default>false</default>
    </values>

This threw an error and there was no support and no explanation at that time.

I suggest you to improve this error message.
Message I got:

Could not parse the XML for 'force-app/main/default/objects/Lead/businessProcesses/Buyer.recordType-meta.xml'. Error occurred at line 71. Further details: An error occurred while parsing EntityName. Line 71, position 29.

File, line and position it's ok. maybe a link to Gearset docs with walkthrough with this probable cause when a parsing error happens.

In a CI job, using source control as the source and including deleted items, you can run into an issue where objects from managed packages show as "deleted" in terms of custom object permissions from permission sets that have access to them. This can occur for permission sets designed to give access to managed package features or if you have a permission set with "View all data" or a system permission that gives them access to all objects in some capacity (read, write).

Ideally, we wouldn't have to include managed package object permissions into Source Control (likewise, Gearset suggests only including installed package metadata versus the details of said package).

It'd be great if Gearset would exclude the custom object permissions being deleted if it's related to an object in a managed package

OR

Add a blocker/warning about trying to remove custom object read permission on a permission set that needs access to all objects (with "View all Data")

In the situation where a repository is the source and an org is the target, there may be a situation where a record type doesn't exist in the repository but references in the layout permissions and custom object permissions do still exist.

Currently, the problem analyzer will catch the custom object permissions and ask you to remove the references to the record type that doesn't exist in the target.

However, it doesn't catch the layout permissions and the deployment could fail with an invalid reference.

In the absence of the record type in the repository, the "Problem Analyzer for excluding the Record Type from the Layout Permission" should trigger in the same way that the " Problem Analyzer for excluding the Record Type from the Custom Object Permission" behaves.