Salt Project vs. Microsoft Visual SourceSafe (Discontinued)

Managing heterogeneous environments of large numbers of nodes, especially nodes which may need sudden changes (security updates, for instance), or frequent replacement, is a strength for Saltstack. Simplicity is not a strength for Saltstack. In a homogenous environment (all CentOS 7, for example, with no Debian or Windows) I might recommend using Ansible instead - it is less flexible and granular, but simpler to configure.

Incentivized

The only time I could recommend Microsoft Visual SourceSafe would be for a beginner who has a small amount of code that they would like to keep track of. This solution would not be recommended for an enterprise or any shop where you have multiple developers working on the same solution.

Incentivized

• A superb remote execution framework! SaltStack allows us to easily program numerous functions on top of it. For example, we developed a fast parallel asynchronous deployment tool that handles all software deployment, including interdependent service management.
• Configuration management is now easy. We take advantage of this to automate (in tandem with AWS tools) the stand-up of all servers and services. It is also relatively easy to create new configuration management states for software not yet supported by the community (e.g. Grafana).
• Flexibility. Numerous small utilities have been built which simply wrap around SaltStack to allow tedious tasks to become easy.

Incentivized

• avoid losing code
• versioning of previous projects
• saving versions on db

Incentivized

• Managing network hardware should be more native and easy
• SaltStack should buffer jobs and, when a client returns, make sure it is executed proberly
• SaltStack should provide basic pillar and states structures to help get newbies started

Incentivized

• Becoming corrupt and having to be rebuild from a previous version.
• It can be extremely slow to check in & out of.
• Lost support several years ago from Microsoft.

Overall Microsoft Visual Source Safe is very easy to use. It is a simple application that does only one thing. It has the basic windows tree structure for listing projects and solutions. There is no way to search for a particular file, project or solution. There is also no way to search the code in the files.

Incentivized

We haven't had to spend a lot of time talking to support, and we've only had one issue, which, when dealing with other vendors is actually not that bad of an experience.

There is no longer support for Visual SourceSafe as I believe it's been retired. There are, however, users that still use the tool and they do help if there are questions or complaints.

I've used shell scripts over ssh, custom in-house deployment tools, Chef, and SaltStack. I've evaluated Ansible, but I was never happy with performance over SSH. Chef's loose configuration data model and lack of philosophy and conventions around use makes it difficult for a team to share responsibility for configuration code. Needing to use additional tools to do orchestration for cross-host/agent dependency relationships made me look for more. SaltStack, while not as mature when I first tried it, impressed me with its speed and elegant design

Incentivized

Azure DevOps is a much better, more modern tool that Visual SourceSafe and everyone should be moving to it. Most if not all the integration that is there can be done or emulated in it

• SaltStack has reduced the time it takes to deploy new machines for us 10-fold.
• It is much easier for us to maintain compliance with industry standards with SaltStack.
• No negative impacts!

Incentivized

• When we started using it, it allowed us to do source code versioning and store the code in a centralized location and not locally.
• We are using it for very few projects with few developers that still maintain those applications and do not have time to merge the source code to Git.

Incentivized