TrustRadius Insights for Travis CI are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Business Problems Solved
Travis CI has become an invaluable tool for projects with limited budgets and resources, offering a range of benefits to its users. The ability to define multiple environments for running test suites has proven particularly beneficial, allowing developers to thoroughly test their code in different scenarios. By integrating with Git repositories, Travis CI enables parallel testing and provides immediate feedback on test failures directly in pull requests. This streamlines the development process and helps catch and fix issues early on. Additionally, users receive email notifications with detailed information about failed tests, as well as notifications when tests pass again, ensuring that they are always informed about the status of their builds.
One major advantage of using Travis CI is the elimination of the need to install various environments and versions locally. This simplifies the developer experience and saves time, especially when working on projects that require compatibility testing across different platforms. Furthermore, Travis CI supports continuous integration and deployment, promoting high-quality standards by automatically running tests and promptly alerting developers to any failures. This has proven particularly helpful for releasing new versions of APIs frequently, ensuring that changes are thoroughly tested before being deployed.
Travis CI's popularity among public GitHub projects is also attributed to its efficient continuous integration capabilities. Renowned organizations like Kubernetes and OpenShift rely on Travis CI for their GitHub repositories. While larger projects may opt for Jenkins due to its customizable build environment, Travis CI remains a popular choice, thanks to its seamless integration with Git repositories and user-friendly interface.
The use cases for Travis CI extend beyond mere testing and integration. Many teams leverage it as part of their code review process, automating builds and ensuring that the test suite passes before starting reviews. Travis CI plays a crucial role in automating the deployment process upon successful merging of pull requests. It is often utilized in both app builds and UI assets, running tests on every commit and preventing merges to the master branch in case of failed builds.
Travis CI is not limited to private projects; it also contributes to the development of numerous open-source projects, such as nodetrine. Its robust CI/CD pipeline allows for rapid changes and ensures higher quality in webpage development projects. Some teams even employ Travis CI as a legacy deployment system, automating their deployment processes with ease.
While Travis CI continues to be a reliable choice for many organizations and developers, the emergence of other innovative tools has led to a reduction in its usage for automated deployments in some teams. However, it remains a go-to solution for continuous integration and testing, especially for those working on public GitHub repositories and projects with limited resources or tight budgets.
Overall, Travis CI covers a wide range of use cases and has proven to be a valuable asset for developers. Its seamless integration with Git repositories, ability to define multiple environments for testing, and immediate feedback on test failures make it an efficient and user-friendly choice. Whether it's automating builds, ensuring code quality through continuous integration, or facilitating rapid deployment, Travis CI has consistently provided developers with the tools they need to streamline their development process and deliver high-quality software. Despite reduced usage in some areas, Travis CI remains a popular choice in the development community, especially for public GitHub projects and those seeking an intuitive and cost-effective continuous integration solution.
TravisCI is being used as a legacy deployment system by a few of our teams in our organization. The business problems it intended to address was an automated deployment process for our project. It is used by a few teams but slowly has simmered down because of our transition to other tools that are still being innovated upon.
Pros
deployment management and statistics
automated deployment
image building
Cons
product design
graphical user interface
more innovative/new features
Likelihood to Recommend
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.
We use Travis CI for both our main app build and all the UI assets. It's set up to run on every commit, and a failed build will stop any merges to master.
Pros
Simple to set up.
Good documentation.
Clean interface.
Good level of customization.
Cons
Speed.
Job scheduling.
Integrations.
Likelihood to Recommend
[Travis CI is well suited for] Any software build requiring automated testing.
Travis CI has proven to be extremely valuable for projects with tight budgets or resources. It is very easy to define a variety of environments to run your test suite against, and its integration with your Git repo lets you test in parallel. Personally, I use GitHub, and when a test fails, the results show up directly in a pull request. It will also send me an email when tests fail, with all the details, and then again when tests pass again. Travis CI prevents you from having to install different environments and different versions locally and does so in an incredibly intuitive, and visually pleasing [way].
Pros
It is very simple to configure a range of environment versions and settings in a simple YAML file.
It integrates very well with Github, Bitbucket, or a private Git repo.
The Travis CI portal beautifully shows you your history and console logs. Everything is presented in a very clear and intuitive interface.
Cons
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.
<div>We use Travis CI for the automation of builds of all pull requests so we can be sure all tests from our test suit are passing, before we start code review.</div><div>Continuous integration of our projects, testing and automatically deploying into production upon successful merge of pull requests onto our master branches.</div>
Pros
I love the ease of use, the UI is very simple and well thought out, and it is still powerful enough.
It integrates with Slack and keeps us informed of all build's status.
It is easy to integrate with Heroku for deployment once builds have passed all tests.
Cons
I think they could have a cheaper personal plan. I'd love to use Travis on personal projects, but I don't want to publish them nor I can pay $69 a month for personal projects that I don't want to be open source.
There is no interface for configuring repos on Travis CI, you have to do it via a file in the repo. This make configuration very flexible, but also makes it harder for simpler projects and for small tweaks in the configuration.
Likelihood to Recommend
I really recommend it for any open source software, there is no service like it out there. Unfortunately, due to the high price, MVP level startups and personal projects cannot use it, but once you reach a level where you can afford it, you should make the jump immediately, I believe it is the best CI out there.
We've been using Travis CI from day one. We believe continuous integration and continuous deployment are great ways to build a great product for our clients while keeping the quality standard high. Every feature we develop has its own set of tests, and if they fail in Travis CI, everyone's mission is to fix them as soon as possible so that we are back on track. As per the deployment process, we are releasing a new version of our API almost once a day. This is extremely easy if you have the assurance that Travis CI gives you.
Pros
Smooth integration with our GitHub account.
Test environment easy to configure.
Quick and useful notifications when build fails.
Cons
Integration with other repositories.
Support for other languages.
Likelihood to Recommend
If you are developing software using test driven development and want to leverage the use of your cloud platform by deploying quickly and easily with continuous integration and continuous deployment, Travis CI is a great tool for you. I have been using it for many years now and cannot start a new project without it.
At nodetrine (my opensource project) TravisCI is being used to automatically test the releases and notify users so all of them know if that release its good enough to be used on their projects. It does not use deployment strategies since it does not need to deploy the releases to any platform but TravisCI provides a really good platform for it.
Pros
Automate testing
Integration between modules
Automate deployment
Build artifacts for project consumption or community
I used it while consulting on a webpage for a client. It allowed us to set up a solid CICD pipeline for rapidly making changes and ensuring a higher level of quality.
Pros
Easy to setup and customize. It uses a yml file for configuration that lives inside your repo. The yml options are very straight forward and easy to learn.
The web interface is very easy to use and navigate.
It offers lots of different ways of being notified when something in the pipeline fails or succeeds.
Cons
Highly integrated with github, might be more difficult if not using a github repo but haven't yet done such.
I use the open source installation of Travis CI (<a href="https://travis-ci.org/jawnsy" rel="">https://travis-ci.org/jawnsy</a>) for public GitHub projects. It's the de-facto continuous integration tool for public GitHub repositories, as it's free and works pretty well. It's used by a number of organizations that I'm a member of, including Kubernetes (<a href="https://github.com/kubernetes/kubernetes" rel="">https://github.com/kubernetes/kubernetes</a>) and OpenShift (<a href="https://github.com/openshift/origin">https://github.com/openshift/origin</a>), though many larger projects also use Jenkins to provide a more customizable build environment. This can be useful for things like building Amazon Web Services AMIs, integration with external services that Travis doesn't support, etc.
Pros
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).
Cons
It only supports Linux and OS X, so other vendors (like AppVeyor) have to be used for Windows support.
The build matrices can be difficult to set up in the travis.yaml file.
Build queues can be long sometimes, since the open source offering has limited infrastructure. This problem does not affect the commercial offering, however.
Builds are limited to various versions of OS X and Ubuntu; other operating systems can be used for teh build via the Docker support.
Likelihood to Recommend
If you have an open source project on GitHub, Travis is the best option available, and it's in widespread use. There are many examples of usage in open source projects of varying complexity, so it's simple to copy bits and pieces from those. The Travis Build Status badges are beautiful and easy to add. The user interface is great if you need to manually retry builds or check logs. It automatically builds all pull requests in a secure way, so that you can check contributions without paying for your own build infrastructure, and without having to configure/manage it.
