Which is better jenkins of TFS 2015 for CI CD

Question

From the people who've worked on it, say that both give you basically the same features for Continuous Integration. I want to know what are the things that are in Jenkins and not in TFS and the other way around. From what I know release management functionality has been integrated in TFS 2015, also including the tools for the entire DevOps(ALM) Pipeline.

Answer 1

Visual Studio and TFS have been using Release Management as a service since the 2nd update. It helps automate testing and deployment of your application in different environments. It's entirely up to you to fully or partially automate the delivery for on demand deployments. It is one of the fundamental part of DevOps which will helps the team to continuously deliver software at a fast and constant rate. For more info check out Release Management.

In case you've been working with Jenkins and you've build a CI pipeline, TFS has options, it has API's through which you can interact with release services from jenkins in your case. Check: Continuous deployment/delivery with Jenkins and VS Team Services