Travis CI is an open source continuous integration platform, that enables users to run and test simultaneously on different environments, and automatically catch code failures and bugs.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Principal Software Engineer in Engineering at AKQA (1-10 employees employees)
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.
Return on Investment
Depending on the type of project, Travis CI can drastically reduce the need for QA resources.
Travis CI can be a very powerful part of your deployment pipeline.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
CTO in Information Technology at Jura Online (11-50 employees employees)
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.
Return on Investment
It saves you in infrastructure and setup costs, since running a server and installing and maintaining Jenkins can be a hassle.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Software Engineer - OpenShift in Engineering at Red Hat (5001-10,000 employees employees)
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.
Return on Investment
It's improved my ability to deliver working code, increasing my development velocity.
It increases confidence that your own work (and those of external contributors) does not have any obvious bugs, provided you have sufficient test coverage.
It helps to ensure consistent standards across a team (you can integrate process elements like "go lint" and other style checks as part of your build).
It's zero-cost for public/open source projects, so the only investment is a few minutes setting up a build configuration file (hence the return is very high).
The .travis.yml file is a great way for onboarding new developers, since it shows how to bootstrap a build environment and run a build "from scratch".
Alternatives Considered
AppVeyor, CircleCI, Drone and Jenkins
Other Software Used
Gradle, Docker, Kubernetes, Apache Maven
Related Products
Products similar to Travis CI that may also meet your needs.