Travis CI Reviews

Travis is a very practical service to automate pipelines, it's based on standard technologies and provides robust integration support with any other cloud provider. From a technical perspective.

Building automation in a cloud-based service implies the latency of moving things over the internet so depending on the size of the build one could feel it takes time. I find the logs feature simple in the end it fulfills its purpose but a smarter tool would add more value.

Pipeline automation for various react and node-based web apps, integrated with AWS and GCP workloads, I believe Travis does great with these integrations and many other services along the way as github, 1password, cloudWatch, eks, etc.

What I like most is the option to comply entirely free for open code projects.

For users who start trial credits end quite fast above all if they use macOS servers

I can compile multiplatform applications in the cloud without having to install different operating systems on my machine. All this automatically and integrated with git

Integración continua y despliegues de forma rápida con muchas tecnologías: Heroku, GitHub, Slack entre muchos otros. Se puede ver el funcionamiento de las aplicaciones en tan solo minutos. Manejo de repositorios y notificaciones vía correo.

La versión gratuita no posee repositorios privados.

La versión paga ofrece mejor calidad de respuesta a nivel de servidores y colocar repositorios privados para tu empresa.

Hacer pruebas de FrontEnd y BackEnd integrando aplicaciones, viendo resultados de manera rápida y sin complicaciones.

When used in conjunction with GIT and any IDE that supports it is very easy to automate tasks of the continuous development pipeline and with that free mental resources to actually work in the idea that you want to implement thru code since you can get notifications whenever something relevant for you is getting changed.

In a perfect world, Travis will work on its own without minimal human interaction, and with experienced teams that is usually the case but when dealing with new developers or with those that are not accustomed to the CI/CD pipeline it is kind of not intuitive and takes some time to get used to it.

It is great to automate tests in any CI/CD project as long as you understand how it works

It's a great tool if you are building with CI/CD in mind

Its fast, flexible and all configuration (except credentials) are store with your source code.

It does not support nested virtualization.

It is very easy to get started as it has very good integration with github.

CI/CD.

All build and deploy operation for my software projects are fully automated and test on multiple platforms.

Simple to use and manage, helps a lot continus integration. It's a must-have!

A bit complex for beginners to setup and understand how to write travis.yml.

Study how it works, and you can easily build, track and manage your software.

Helps me with CI, i can easily track if a commit has some bug, and i can easily test more language's version in one time.

I really liked using Travis CI when I wanted to deploy changes to the open-source project I was working on - it was very easy to pinpoint which exact tests failed and where I had to go back to fix them before deploying.

It takes a very long time to run through the tests for some reason - the project I worked on was fairly small so I wasn't sure why it took 2 - 3 minutes just to run tests (this also slowed down our productivity in general, although I know there were other ways to run tests running it on Travis was visually the best to see what the outputs were). Additionally, even if the tests did all pass, there were still many moments that the tests didn't catch which made our website go down.

My team used data from libraries from the IT team on campus to find spots on campus that were not being used so users could easily find unused rooms. Our specific project was to predict which spots would be free using past data. The benefits I realized was that deploying was fairly simple.

Awesome to run unit and integration tests after each commit and can be used with Github easily with few configurations.

Don't have thing to dislike just learn how to configure.

Try to use it in projects as it makes life easier and not expensive.

Used to help with build automation after each commit also to run tests as well as helping with deployment.

Most of the open source libraries use TravisCI - that's what makes TravisCI pretty - love how they support open source community.

Had some troubles time ago to set up a private repository - not sure how it's working for private one now on - but it was so complicated awhile ago.

If you do have an open source library, go ahead and use TravisCI, please do what the most the open source libraries are doing.

All my open source libraries use TravisCI - just for open source libraries hosted by GitHub

Travis CI is best continuous integration tools especially you can easily test your product within different environments.

I didn't find any bad behavior in this project.

When you have a software that supports multiple version(python2.6 python3.5 ... etc), Travis Ci is the best for your continuous integration tests.

Test product easily with multiple environments. (MongoDB v2.6, v3.2, v3.4 etc)