Reputation: 694
I am considering how practical it would be for our company to utilize Visual Studio Team Services as our build controller.
We currently utilize SVN as our repository, and JIRA as our change control / bug reporting agent. We have no real desire to change this process at this time.
Everything I have seen so far works on the premise that Team Services is utilized as the source control and change control agent. I realize that I can utilize a SVN task in MSBuild, but can I integrate this somehow into a trigger for a build?
Is it possible to use Team Services just as the CI build controller?
Upvotes: 0
Views: 248
Reputation: 328
I don't know of a trigger. An alternative to try, which may seem like over kill. Create an empty project in Team Services, setup a tool like SvnTFSSync, and essentially sync your SVN to Team Services checkins. Once you do that, you can setup Team Services checkin triggers to automate the build.
Like James Reed said, with Team Services in this case, its all or nothing really.
Upvotes: 0
Reputation: 14052
In this aspect Team Services is all or nothing. It's an integrated solution and Source Control is at the heart of that.
Team Services has 2 types of Source Control. A centralized repository which is very similar to SVN, and as of TFS 2013 you can also host a Git repository within Team Services.
If you want to use Team Services as a build engine then you need to migrate your source in to one of these kinds of repository.
I would say that if you're already using SVN and Jira, and you're happy with that, then there is very little reason to migrate to Team Services. Something like Team City, Jenkins or CCNet is your best bet.
Upvotes: 1