Is anyone familiar with AutoDesk Vault that can give me some pros and cons of using it for source code version control? I'm guessing it's mostly cons since Vault is designed for CAD files.
The company I work for has gotten serious about flexibly standardizing the new product development process throughout the company (80+ divisions). They're rolling out a web based project management site with a SharePoint back-end and they are also starting to enforce using Vault. Most of our products do not involve software and so source code control has been kind of overlooked. All I get is "Vault can handle text files", but there's more to version control than just comparing a single file.
Can Vault:
- Integrate with Visual Studio or Eclipse or any IDE?
- Compare different historical versions of the same file?
- Branch, merge, tag?
- Link code changes with requirements?
- Import libraries/code from other repositories with a single checkout?
- Run hook scripts?
- Any other considerations...
Since corporate is still pre-roll-out, I'd rather get a proper version control system implemented, rather than try to jerry-rig an inadequate tool.
Thanks
Aucun commentaire:
Enregistrer un commentaire