Azure DevOps Services vs. Travis CI

ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.

TravisCI is suited for workflows involving typical software development but unfortunately I think the software needs more improvement to be up to date with current development systems and TravisCI hasn't been improving much in that space in terms of integrations.

Incentivized

• Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
• Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
• Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.

Incentivized

• It's simple and easy to get started (it can detect the language being used based on build configuration files like a Maven pom.xml).
• It's free (as in beer) for open source projects.
• It has a responsive staff (you can file issues on GitHub to ask for new languages or packages to be supported, and the turnaround time isn't too bad for the free offering).
• The user interface is beautiful and easy-to-use, including features like live-tailing in-progress builds.
• It supports specifying private environment variables and encrypted credentials, so that you can safely automate deployments (for example, pushing built docker images to DockerHub).

Incentivized

• Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
• Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
• Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
• With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
• If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade

Incentivized

• Travis CI is a fairly mature platform now, and most, if not all of the common complaints have been improved. This includes documentation and logs with color support.

Incentivized

I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.

Incentivized

Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.

Incentivized

TravisCI hasn't had much changes made to its software and has thus fallen behind compared to many other CI/CD applications out there. I can only give it a 5 because it does what it is supposed to do but lacks product innovation.

Incentivized

When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.

Incentivized

After the private equity firm had bought this company the innovation and support has really gone downhill a lot. I am not a fan that they have gutted the software trying to make money from it and put innovation and product development second.

Incentivized

Was not part of the process.

Incentivized

Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing interfaces, I feel it would be a complete project management system.

Incentivized

Jenkins is probably the leading choice for automation and has loads of features and a large community behind it, but it can be overkill for many projects. It also has more of a web 1.0 look and interface. CircleCI is another similar big competitor, but cannot compete with Travis CI's free account [in my opinion].

Incentivized

• Increased dev team efficiency through more streamlined development processes and task automation.
• Improved quality of software deployments due to better source control, automated testing, and release management options available in DevOps.
• Better collaboration between the dev team, business analysts, and agile project managers.

Incentivized

• It saves you in infrastructure and setup costs, since running a server and installing and maintaining Jenkins can be a hassle.

Incentivized