configure which problem analyzer results to use in CI jobs
Being able to configure which problem analyser results to use in CI jobs.
For instance, we can’t deploy any changes to managed packages because the problem analyser will ignore them (even though we have components from a managed package that we can modify and deploy without issues), that would help to reduce our manual steps during deployments.
If providing the possibility to specify which rules we want to apply in a CI job is too complex, another alternative is to provide the option to disable it completely if we want to.
Often, the analyzer generates more issues than solving them. We don't want to have a green build at any cost (skipped components, manual steps, etc.). It would make more sense to have the option to disable it and let the build fail if something is wrong.
The analyzer is a good idea during compare and deploy since you can be advised about things you might be doing wrong and that's the correct moment to apply these rules.
In the current situation, we end up with a repository with unused/orphan metadata which won't be ever deployed and we never know what was the final result of the deployment (you don't even see in the deployment report which components were skipped because of the analyzers.
Sorry for the silence on this folks - this is indeed something we've been looking into, but we've pushed back the shape date a little from Q1.
I'd really appreciate it if you could drop us a message in the in-app chat to tell us exactly what problems the analyzers are (ironically) causing here - we're happy to ship a feature to disable specific analyzers, but if there are analyzers that are stopping your CI job from working then there's a good chance the best solution is for us to tweak the behavior of that analyzer, rather than disable it. We've already made a couple of changes to existing analyzers for this reason, so the more information you can share, the easier it'll be for us to proceed. I suspect the best solution will be to both improve the behavior of the problematic analyzers, and to expose the ability to disable certain analyzers in CI jobs.
Martin Novacek commented
Based on the Roadmap: https://gearset.com/roadmap for Q1 the "Ability to control which problem analyzers run during CI" should come soon. Correct?
Currently we have a "managed package" in our repo and we are not able to deploy this "managed package" picklist values.
andrea huetson commented
This issue has been a consistent problem with some deployments. I would be nice to be able to turn it off when necessary but still have the option to have it on to see suggested fixes. Our work around building out a custom filter is time consuming and is not proving to be of much value.
Adding the option to disable the problem analyzer would be also valid. Right now this is something that is frustating us to the point of considering a change of deployment tool.