EMCO MSI Package Builder vs. JFrog Artifactory

For large, complex software deployments that have a number of install scenarios and executables that interact with one another, EMCO MSI Builder is well-suited. It is able to track software installs, registry changes, file additions, and deletions, modifying shortcuts and anything else that would be needed to prepare big deployment projects for large organizations.

Incentivized

It works at scale and a large number of accessible pipelines for searching, repository updates and indexing will become easier. JFrog provides end-to-end solutions for all DevOps needs. With this, Jfrog Artifactory specifically implements the management of highly available repositories, with a smooth interface and integration with all the main CI tools on the market.

Incentivized

• Capture Customizations to settings/registry.
• Track File movement and additions during install for specific uses.
• Capture file and system level changes for inclusion in deployment.

Incentivized

• Artifactory Management acting as a repository manager of docker images, application and component dependencies
• Automate pipelines and thereby releasing changes faster
• Supports high availability and scalability with multi site replication

Incentivized

• Work on clearly defining functions on reboot.

Incentivized

• We can always use support for more different types of packages in Artifactory.
• We also would like to see the Artifactory X-Ray produce continue to mature.

Incentivized

The main problem that seems intractable is getting the checksum of the artifact. Managing container artifacts is a game changer for us during project execution, as the container artifact type exposes all base image and Docker file steps. This makes debugging or analysis easier. Jfrog Artifactory provides promotion feature and can automated from one environment repo to another environment repo before the deployment occurs.

Incentivized

Support has always been quick to respond with additional information and clarification

Incentivized

Support tickets take days to respond. The most basic of questions that should be knocked out in a few hours don't get answers for days. Tickets are also closed without resolution.

Provides advanced functionality for the enterprise level software deployment analyst over and above the basic tools that Microsoft included with the original APP-v sequencing tool, allowing the analyst greater control over what is captured and how it is captured. This makes the impact of needing to change the deployment package easier to maintain and update

Incentivized

JFrog Artifactory has a much more friendly GUI, making package exploration less of a chore to do. Other than that, their features are pretty much comparable to each other. Both support multiple types of packages; both have API that can integrate well with CI/CD pipelines.

Incentivized

• It allows faster turnaround time for complex deployment projects.
• Easy to update existing deployment packages with changes.
• We must maintain the pristine virtual machine for usage.

Incentivized

• So many times it happens at the time of dependency resolution some of the servers are down e.g NPM, Maven central, PiPy in that cause our builds starts failing. By proxying these repositories with JFrog this is never happened again.
• It reduced the additional cost of container image registry and management effort.
• Support of integration with Build, Monitoring, and CI tools resulted in smooth automation and management.

Incentivized