Subversion integration with Visual Studio Team Services
November 18, 2015
While all of the recent talk in the Java world about version control systems centers on Git, Subversion is still very much in use across the industry. Today we are announcing that Team Foundation Server and Visual Studio Team Services provides Team Build support for Subversion. With the release of Team Foundation Server 2015 Update 1 and soon with Visual Studio Team Services, Subversion can be chosen as the source code Repository on every build definition. You now get all of the benefits from using the new scriptable, cross-platform build system with your existing Subversion repositories.
When adding support for Subversion, we have also included mappings support (which allows you to map only the buildable subset of sources you need for a particular subsystem in your repository), centralized management of the credentials used to connect to both on-premises and hosted Subversion repositories, as well as support for scheduled and continuous integration builds via polling.
We have posted a detailed walkthrough for the new Subversion support on the Visual Studio Team Services for Java site. Also be sure to learn more about the new build system.
The Java ALM team at Microsoft is very excited to announce the Subversion support and hope that you can integrate it into your development workflows!
That's great to hear. Please note however that this news should be in no way Java related. We're using a Microsoft stack with WinForms, WPF, SQL Server, ASP.NET MVC and Web API all connected up to TFS on premise. But we would never use TFS source control. It's SVN all over the place with GIT for new development.
No help. We have existing SVN, no TFS projects, or TFS knowledge. Visual SVN for Windows 10 is an epic failure. The getting started sub link requires 3 separate accounts to be setup!???? What's the point of adding SVN if there is no help to use it.
@MSt: Thanks for leaving a comment! Yes, we're well aware that non-Java solutions are managed in Subversion too. Being a part of the Java ALM team, I let a bit of that enthusiasm through in the article. 🙂 Thanks for making that point.
@WTF:
The "Getting Started" section on the Java site shows you how to take an existing code project that we provide (there's a link to download the source) and get it building with Visual Studio Team Services (VSTS). To use VSTS, you do need a couple of accounts. You need a Microsoft Account that you'll use to create the VSTS account (so that you can create team projects, etc.). If you want to deploy the sample to Azure (which is purely optional), you'll also need an Azure account. If you don't want to deploy to Azure, just skip those steps. Also, in the "Next Steps" section of the Subversion walkthrough (linked above), there's a YouTube video that shows how to set up the build definition that pulls the source code out of a Subversion repository.