Compare Azure DevOps Server and Jenkins 
- Users report that Azure DevOps Server excels in its "Pipeline Control" feature, scoring 8.9, which allows for seamless management of CI/CD pipelines, while Jenkins, although strong, has a slightly lower score of 8.7 in this area.
- Reviewers mention that Azure DevOps Server's "Deployment-Ready Staging" feature is highly rated at 8.9, providing a robust environment for testing before production, whereas Jenkins users note a score of 8.6, indicating it may require more manual setup for similar functionality.
- G2 users highlight Azure DevOps Server's superior "Quality of Support" with a score of 8.2, which is appreciated for its responsiveness and helpfulness, while Jenkins users report a lower score of 7.8, suggesting that support may not be as readily available or effective.
- Users on G2 indicate that Jenkins shines in "Integrations," scoring 9.2, which allows for a wide range of plugins and third-party tools, making it highly customizable, while Azure DevOps Server scores 8.9, showing it is also strong but not as extensive in this area.
- Reviewers mention that Azure DevOps Server's "Automation" capabilities are rated at 8.8, providing a user-friendly experience for automating workflows, while Jenkins users report a higher score of 9.2, indicating a more powerful automation framework, albeit with a steeper learning curve.
- Users say that Azure DevOps Server's "Processes and Workflow" feature is rated at 8.9, which is praised for its intuitive design, while Jenkins, with a score of 8.4, may require additional configuration to achieve similar workflow management efficiency.
I love TFS. I love the way it tracks bugs, I love the way it manages and tracks deployments to different environments, and I love the way it manages test cases, test plans, requirements, and features, as well as tasks. Our company currently has it set up so...
The thing with TFS is that it seems to require a lot of manteinance and configuration because most of the times even setting up a new project is a mess that causes the code to be copied multiple times over the computer's filesystem, some files are ignored...
The ease of setup and configuration of new builds. I love the ability to copy builds to create new ones.
Markup. All the configuration is stored in XML, which imho is overkill for what Jenkins does. It also makes version control awkward. I really wish I could use git to keep track of versions of jobs and also as deployment method. Linux sys admins tend to live...
I love TFS. I love the way it tracks bugs, I love the way it manages and tracks deployments to different environments, and I love the way it manages test cases, test plans, requirements, and features, as well as tasks. Our company currently has it set up so...
The ease of setup and configuration of new builds. I love the ability to copy builds to create new ones.
The thing with TFS is that it seems to require a lot of manteinance and configuration because most of the times even setting up a new project is a mess that causes the code to be copied multiple times over the computer's filesystem, some files are ignored...
Markup. All the configuration is stored in XML, which imho is overkill for what Jenkins does. It also makes version control awkward. I really wish I could use git to keep track of versions of jobs and also as deployment method. Linux sys admins tend to live...
