Azure Pipelines vs. Travis CI

With a fully Microsoft Azure based workflow - Azure Pipelines makes absolute sense. Azure Pipelines are robust and work very well with SonarQube for test coverage and are shared with our developers. This prevents the developers for pushing code without unit tests across our backend and frontend platforms. We have reduced our instances of manual regression tests especially when there are multiple teams working across the same repositories.

Incentivized

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

• Code Integration/Code Deployment
• Azure Engine Auto Scaling Up with help of Pipeline
• Managing Version Control and deploy in rollback with just one click

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

• Error messaging when team members don't have permissions

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

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

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

We have used the GitHub CI/CD. Earlier we were using the Azure Pipelines but after GitHub had their actions, we integrated that for CI/CD. It runs the tests and makes a production build which can be live. GitHub CI/CD is more useful because we have to make script only once then just by few changes we can deploy it onto Azure, AWS, Google anywhere so we found it more convenient

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

• We don't have to deploy changes manually
• But because of this that we automated some tasks, we need to be still aware of some edge cases we can meet and which can cause a pipelines failures
• We can deploy changes pretty fast

Incentivized

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

Incentivized