Kenny
My feedback
8 results found
-
10 votes
An error occurred while saving the comment Kenny
supported this idea
·
-
11 votes
An error occurred while saving the comment Kenny
commented
Since Test Suites can be managed via source code, this would also allow the ability to determine flexible test runs during deployment instead of needing to manually define them as part of the gearset CI job
Kenny
supported this idea
·
-
11 votes
An error occurred while saving the comment Kenny
commented
Absolutely! As part of integrating multiple tools in a CI/CD Pipeline, sending detailed status back to other systems is imperative. Thanks!
Kenny
supported this idea
·
-
3 votes
An error occurred while saving the comment Kenny
commented
Yes, please!
Or implement related idea: https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/36021976-export-pmd-rulesets-configuration-as-xml-file
Kenny
supported this idea
·
-
4 votesKenny
shared this idea
·
-
30 votesKenny
supported this idea
·
-
29 votes
An error occurred while saving the comment Kenny
commented
Yes, Please! These are supported natively in SF API now as per: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_territory.htm
Please add this component type to your list!
Thanks!
Kenny
supported this idea
·
-
68 votes
Thanks for the suggestion.
We have plans to improve the way the diff viewer handles changes and whitespace in the future, though it’s not currently under development.
Thanks,
Jason.Kenny
supported this idea
·
Yes! This would be a huge timesaver! I'd rename the title "Option to ignore Package Versions during comparison" Most of the time, our deployment does not depend on the package versions so, being able to ignore is helpful.
When things like NPSP get upgraded, suddenly, I have 95 differences in my comparison! these diffs won't affect functionality at all and require a lot of manual intervention to ignore, instead of enabling better CI automation.