Analyze multiple solutions

[rappen]

Add the possibility to select multiple solutions (or local solution files) for analysis.

[rappen]

@mhuguet Is there any guidance on when to use the option of uploading solution files one by one and passing multiple uris to the analysis, and when to zip solutions together and upload/analyze that combined file?

[mhuguet]

There is nothing really special about it. It is just a batching mechanism. We do run them in parallel so it just reduces the need for any logic on the client. One suggestion is to keep it to 10 or under, however, we've had customers send 100+ in, but I'd rather that not be the case. :)

Something to note about the artifact sent to the service. It can be a solution zip or cab file, a package, or a zip file containing any solutions. We have rules that we use internally that I'd love to make available publicly that compare a base solution and a patch to look for problematic behaviors in the patch. This is the main reason for having support for a zip of solutions. It also allows for cross solution analysis where you may have components that make up your "thing" in multiple solutions as we have traditionally done in CRM/CE. For example, one solution has the plugins, another has the entities, and another has the message processing steps that link them together. If passed in a single zip file, our parser will do some basic "stitching" together so the rules can analyzing accordingly.