VersionVault Dynamic Views rely on a virtual file system to provision assets to the workspace so that files are available for use instantaneously and you can immediately start browsing, editing, or executing tools to perform builds or simulations. With most other configuration management systems, you’ll be waiting for files to be copied, or links to be created before you can begin work. VersionVault Dynamic Views support this kind of functionality in a LAN environment. VersionVault also has Automatic Views that rely on similar technology for similar benefits in a WAN deployment.
VersionVault has a very flexible deployment model. For a small organization in a single location, a local area network is sufficient. If there are small teams scattered around specific geo, VersionVault supports a centralized server with LAN and WAN connectivity as needed. For global development where WAN connectivity can be challenging, VersionVault Enterprise supports automated replication of repository data. Any or all these deployment models can be used alone or together in the same deployment.
One of the reasons VersionVault is a great system to get started with is that it can support unlimited growth. From one user to tens of thousands of users, VersionVault can provide a configuration management infrastructure without limits. Large files, large binary files, large workspaces, global deployments… None of these are a problem for VersionVault.
For regulated industries, VersionVault provides everything you need to meet regulatory requirements. Every change is captured, logged and secure. Every build of a “derived object” can automatically create a configuration record with every tool version and every file version used in its creation recorded. In addition to other methods, the configuration record may be used for comparison purposes when a build goes bad, making it very easy to find what change caused the problem. Every configuration, which may consist of hundreds of thousands of files, can be recreated instantaneously, whether the configuration was created yesterday, or a decade ago.
Extensive support for parallel development, especially when merging. VersionVault’s “common ancestor algorithm” can trace back in an element’s history to a common source making automatic merges possible, and manual merges more focused and accurate. VersionVault’s graphical merge tools support multi-way merges of up to 16 branches, but hopefully you’ll never need that! While most systems support merging of textual information, sometimes the assets being merged require special handling because they contain custom or structured data. VersionVault supports the creation and addition of custom diff and merge algorithms so that any file can be usefully compared and merged.
VersionVault versions directories, and therefore can also track changes to the namespace, like renaming files and reorganizing the directory structure. This is especially important when working with languages like Java, where files get renamed when language elements like class names and package names change. With this additional information it is much easier to understand what changed during a merge where the namespaces differ between the branches.
VersionVault implements a model for asset development that supports both private and shared branches, supporting teams that want to keep changes segregated until they are explicitly delivered to the team branch and then selectively merged back into an individual engineer’s branch, or teams that want changes to be visible to the team as soon as they are checked in. VersionVault also implements a hierarchical, reusable organization of components, making it easier for an organization to reuse components across projects. If UCM is too constraining, VersionVault also supports the creation of a custom process model using commonly understood configuration management concepts like branches and labels.
Protecting your IP is critical, not only from external attacks or intruders, but also internally between projects and teams, and third-party contractors with whom you have a relationship. VersionVault allows you to create role-based specifications of access control, and reuse that specification across teams by assigning users to roles for each team. Access control can be modified at any level of the asset hierarchy, or inherited through the hierarchy if desired.
Not only does VersionVault support a complete and powerful command line interface, it also has GUIs for those users that prefer working with higher-level interfaces that can guide them in using the system. The GUIs support all operations typically performed by developers and project leads. In addition, where graphical user interfaces help the user to visualize complex data, those interfaces are also available from the command line interfaces.
VersionVault supports integrations with popular IDEs like Visual Studio and Eclipse. Teams working in one of these environments can easily access configuration management operations as they’re working directly with their assets. No need to change applications or views within the IDE
Complete, automated repository replication for global development where performance is critical
Replicate only those repositories needed remotely to protect intellectual property
Manage independent work at each replica and integrate it with all other work from other replicas