Menu
We have appointed a new team lead who will be starting in the next few weeks. He has previously worked with TFS and is likely to want to use that for CI. The team is new to continuous integration so will take any advice he gives. Is there any reason to choose another system like CruiseControl or TeamCity, or are the features quite similar? We will be using it in an Agile/Scrum environment. Thanks.
Edit
Are TFS 2010 features much improved from previous versions?
498
Continuous integration should always be used as part of the software development process. Continuous integration is an excellent tool that facilitates better communication and planning. If software developers use CI, they can improve product transparency and foresee any possible problems in the pipeline.
TFS is Microsoft's solution for continuous DevOps and has since been rebranded/renamed Azure DevOps Server. It has an in-built suite of tools that lets you achieve continuous integration and delivery with ease.
Continuous integration (CI) is the practice of automating the integration of code changes from multiple contributors into a single software project. It's a primary DevOps best practice, allowing developers to frequently merge code changes into a central repository where builds and tests then run.
I will default to my "comfortable" answer. If your team doesn't have any strong feelings about it, and TFS is the technology with which your new TL is most comfortable, use TFS. Especially with TFS 2010, it's perfectly adequate for CI.
If your team has objections, I suggest you ask them their reasons and do the research to find which would be better.
146
We are a $2.5B solar manufacturing company using TFS to manage all our software artifacts. We use continuous integration for most of our projects and it works great. We also use it in an Agile/Scrum environment, or at least we're moving in that direction.
35
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
