Travis CI

Travis CI - My Unstoppable open source integration platform.

Kommentare: my overall experience is moderate.

Vorteile:

What I like most is that it takes less time for configuration and It also supports a build matrix feature.

Nachteile:

What I like least is it provides limited support and have less customization options than Jenkins.

The code integrates very well

Kommentare: It has been a very convenient experience, since I can easily see the status of my builds directly from the platform when logging in, it is exactly a good technical process for each build I need, it can be worked very easily in a group.

Vorteile:

Travis CI is a continuous integration tool that I find very useful as a Senior Software Development Engineer at [sensitive content hidden]. I love its ability to automate the entire process of building, testing, and deploying software. With Travis CI, I can be sure that any code changes I make will be seamlessly integrated with the main project and tested automatically.

Nachteile:

Integration with GitHub gives me a lot of errors, when logging in, when linking, when unlinking, that is quite tedious and only specialists on my team have found the solution.

Static matrices and changes to OSS terms mean I cannot recommend the product

Kommentare: Our initial years with Travis were successful, and we were quite happy with the product. But over time, the lack of flexibility meant struggling to create and deploy our CI definitions. But the part that killed Travis for us was the change to OSS terms late in 2020. We'd already noticed that our queues would become long, particularly if we had many contributors or maintainers working simultaneously. But with the changes in terms, we quickly ran into a scenario where we ran out of hours by mid-month. This left us with an untenable situation; as an OSS project, we have limited funds, and we would quickly run through those if we purchased a plan. As a result, we are within 1-2 weeks of moving off the platform entirely.

Vorteile:

When we first started using the product, it was one of the few that existed, and it provided us exactly the assurances we needed to have predictable, stable software releases. Idempotent runs made it possible to know exactly when and why something failed.

Nachteile:

Since we produce OSS libraries, it's important for us to test against each language version we support. Unfortunately, there is no way in Travis to dynamically create a matrix based on the library/package definition itself. For instance, we produce PHP libraries, and our package management solution, Composer, allows us to specify in the package the versions we support. Unfortunately, when we change those, we also need to remember to change the Travis definitions to reflect those changes. This becomes a source of error very quickly - Travis may report all is green, but it turns out we haven't added the new PHP version to the matrix, so it's a false sense of assurance. On top of that, it's impossible to succinctly make discrete jobs that do different things. For instance, I don't need to run coding standards checks, static analysis, and documentation linting for every single job in the matrix; I really only need to run these once. But to do that, Travis forces me to define env variables for jobs, and then use conditionals to determine what to run. This makes the CI definitions very convoluted, and, if you have a lot of repositories that need to do the same, hard to distribute when you have changes to make. Other CI systems address this.

Travis CI is great automation tool is easy to configure and run.

Kommentare: We have used Travis ci for automation of code building, testing and deployment. Travis CI is one of the top continuous integration and continuous delivery tool available in the market. We usually use Travis CI for medium scale projects because it easy to use, few minutes of configure is needed comparative to Jenkins which require skilled professional to configure it. We have used it for test projects as it is free for public projects.
Travis Ci is good for small to medium scale projects, which doesn’t require much of the customization or less complex projects. Travis CI is also good for public and open source projects because it provides free tier for public projects. It’s easy to use, you don’t need any professional skill to set it up.

Vorteile:

Great thing about Travis CI is it’s easy to use, easy to configure and start running it, you can easily integrate GitHub account and whenever you push your code its integrated and tested on Travis CI. Travis CI doesn’t need hosting server to run it unlike Jenkins which require hosting server. For public projects you don’t have to pay, its free to use for you test and open source projects. Testing on different environment, devices, OS is optimized and run synchronously. You don’t have to maintain software updates for Travis CI unlike Jenkins. It is fast for testing code on different environment by having different jobs like you can have separate job for unit testing and separate jobs for integration testing.

Nachteile:

Travis CI doesn’t have that much flexibility respect to customization as compare to Jenkins. Integration with third-party tools is not too much which reduces it flexibility. You code is accessible to Travis CI which is not good for most sensitive projects. You must pay for private projects as comparative to Jenkins which is free for private projects.

Travis CI: Great overall for over 8 years. Not anymore after travis-ci.COM migration & OSS credits

Kommentare: Overall, Travis CI used to be the best turnkey solution for independent Open Source developers to set up Continuous Integration and Unit Testing pipelines. Thanks to bad actors such as unscrupulous bitcoin miners, this once great free open source community service has been morphed into a paid credit-based system. Lack of customer support responses have pushed independent volunteer open source developers out. We simply cannot afford CI testing when our software is free and open source by design.

Vorteile:

As a long-time user of TravisCI for 8 years, I loved the ease of setting up CI testing pipelines and testing matrices with a single .travis.yml file. It made testing DevOps Chef cookbooks easy and was a great solution that integrated well with test-kitchen.

Nachteile:

When getting a remote VM testing pipeline set up, there are some barriers to ease of debugging. This was primarily due to the lack of live SSH terminal access to poke around at the testing environment to debug job failures. After they added Debug Mode, this became a bit easier. The main problem with Travis-CI was recently introduced with the travis-ci.COM migration. Users were encouraged to migrate projects over to the new website with no way of going back. A new paid credits system was forcibly implemented, with some promise of Open Source credits. All of my projects on TravisCI were free and OSS licensed, so I asked for OSS credits. After a few back and forth emails, I was promised 25k credits. However, after checking in the OSS credits section I still see zero credits listed. It seems that just like that, Travis CI was taken away from OSS users who chose to migrate with no warning about the implications. Travis CI news blog posts explain that this change was made due to some nefarious bitcoin miners abusing their free build systems to mine cryptocurrency. So just like in school where the bad apple ruins it for the rest of the class, now Travis CI has been taken away from small Open Source developers. Please improve your customer support and reinstate OSS credits for independent Open Source developers! Any kind of response or clarity around the application process would be much appreciated!

Pricing Changes, Botched Rollout

Kommentare: Overall, beyond the pricing switch, I had been very happy with Travis CI. But, after this pricing change without any notice, I have become unhappy with it. At $85/mo to build two projects without any concurrency (it's slow), I'm become less interesting in staying a customer.

Vorteile:

I liked the ease of use getting Travis setup, the caching, and the build matrix.

Nachteile:

I think the concurrency model is terrible. Sometimes when I want to deploy code to staging and production, I have to wait for each PR and commit to build before the push happens. Sometimes this takes 20 minutes for all branches to finish building before a push can happen. Also, I'm very unhappy with the pricing changes roll out. I have been paying for Travis for a couple years now. All of a sudden, my iOS team said they didn't think our builds were working any longer. There were a bunch of builds that didn't go through, saying we didn't have enough credits. Digging in, I realized your pricing model changed. So our builds have not been going through for close to a couple months now. I never received an email that you would be changing the pricing which would then break our builds. This to me is a botched roll out. You should have specifically told me that my iOS builds would stop working. In our dashboard, it just shows that our last build was successful 2 months ago. Not that no more builds were happening. This is unacceptable. So much so, that I am actually now reading the Travis CI to Circle CI migration document. Circle CI seems like a cheaper option for us now.

Used to be one of the only good option, not so much more today

Kommentare: We see it here as less and less professional. It started with a lot of time to get new images, the problem of running after 4PM (Berlin time), the cache for ccache that suddenly disappear (which makes us use even more credits, obviously), and we are missing more and more CD. It really feels as if, after Travis was bought, that the board decided to "cash in" money. You even need to pay credits now for OSS? How is that supporting it?

Vorteile:

I liked the ease to setup a new project with it, once you know how to get around the product.

Nachteile:

For sure this new price plan, that was announced a day *after* it was put in place (seriously?). It costs us more than half of the credits to make just one build. The price per minute is just insane. I can have more workers and unlimited build times with Azure DevOps, for about the same amount of money of just the subscription alone (so not counting those Travis add-ons). When the credits are done, then the CI will just block. You need to close and reopen the PR. Problem is that we have other GitHub integrations, so this makes the process really painful.

Essential for software development

Kommentare: I am able to conduct a wide variety of tasks from checking compilers, running static analysis, and building documentation.

Vorteile:

Travis-CI was the first CI system I used on my research projects, and to this day Travis-CI still does the heavy lifting on most of my tests during Continuous Integration. It's extremely flexible; I have workflows that run static analysis, security checks, documentation builds, and more. The features and integrations with a number of other systems (GitHub, CodeCov, etc.) make this my go-to CI. I especially appreciate the support for Education customers, other CIs would be quite expensive by comparison.

Nachteile:

Operating systems support can lag. In particular, support for modern C++ compilers can be a bit tricky (it's an old item many of us have raised). The new plans price some organizations (e.g. Boost) out of using it. Support on the MacOS images is not as robust.

review

Kommentare: It was amazing until the recent price changes.

Vorteile:

Very easy to setup and many integration examples. Multiple services and environments makes it quick to setup for many testing combinations.

Nachteile:

The pricing has gone up drastically recently and without that much time to adapt. The best way to keep services up and running without getting caught back-and-forth requests of build minutes was to move away from the service.

Lots of features, sometimes build issues, a bit slow

Kommentare: It was a good choice at the time. But I am not sure if there are now better alternatives. I would especially check for a docker based build system.

Vorteile:

Travis has a lot of features which can be setup easily using configuration files. It is free for open source products and not to expensive for company projects.

Nachteile:

Quite often builds are stuck which leads to a huge stop in developments in hour company because we pretty much rely on it. Also the builds starts quite slow.

Great tool for CI/CD

Vorteile:

Travis CI can be easily connected to a GitHub repository, making it easy to automate builds and deployments and guarantee the quality of the code with tests. It also has a big community that helps troubleshoot any issue.

Nachteile:

Travis CI does not offer dedicated build environments for the builds, which means that the builds are impacted by other builds running on the same shared infrastructure.

Hard to beat such an offer when in academia

Kommentare: The reproducibility trend is gaining momentum within the academical research community. CI usage, now a must have for software engineering concerns, can easily be stretched to address reproducibility issues and is thus being rapidly adopted.

Vorteile:

- navigating the smooth and complete interface (with a nice github integration) - logs are detailed, thorough and hosted for a long time - jobs don't get to wait for long delays once triggered - great (and generous) customer support - nothing to install on premises

Nachteile:

Every CI offer must face quite technical challenges to address specific/advanced services like dealing with credentials or managing sophisticated job workflows. Travis CI does the job quite nicely on such issues yet the learning curve can be quite steep at first. Yes, Travis CI does offer a thorough documentation, yet getting all the tidbits properly aligned can be a tedious task at first (your mileage may vary).

Nice GitHub Integration

Vorteile:

I like that I can see the live status from GitHub and that the UI is very simple. I can easily find everything. The console output is colorized (it's not in other CI software I've used).

Nachteile:

Sometimes parts of log output is collapsed, which has hidden an error for me before. It took a while, but my team figured it out.

Works, but deprecated UI

Vorteile:

It does the job with reliability. I have no reason to change.

Nachteile:

The UI has not evolved for years I think. I'm constantly doing the same 10 clicks to do the same things everyday, that I could have done in 1-click with a better UI. There are no insights, no "nice to have". It may work but I have absolutely no attachment to the product and could change without missing anything. In fact, I'll probably rationalize the number of tools we have by switching to Heroku CI or Github Actions, since they do as much as Travis I have no need for another tool.

It's awful, but we are stuck with it

Kommentare: I hate using it, I never would have recommended it, I want our team off it as soon as possible but the one person that set it up refuses to look at anything else and has the bosses ear. So I'm stuck with this nightmare of a build system that is just AWFUL

Vorteile:

Nothing... I hate this platform. Gitlab is way better for CI/CD

Nachteile:

Everything, but mostly, debugging build issues and that build environments aren't cached from build to build and have to be completely rebuilt every time and for no reason seem to fail for random issues. Like not being able to download a dependency. Or failing to deploy to github releases without an helpful error messages. Or worse, saying you did deploy, but then the package is nowhere to be found, and there is no way to debug this

Travis CI review

Vorteile:

This tool is best for mobile app automation. It supports native iOS, Android and other cross-platform like flutter.

Nachteile:

More number of builds are not supporter for a free/indie account.

The long-standing king of open source CI/CD... but will it last?

Vorteile:

Been using Travis-CI for about 8 years now, and it's always reliably hosted my OSS projects.

Nachteile:

Now with new ownership we've been seeing more downtime. Hope they can keep it afloat!

why do i need a title? 🤔

Kommentare: very happy

Vorteile:

I like that it gives a pride option :D checking previous builds, who issues them and if the failed/passed is very nice. for the most part is is smooth and just does its job.

Nachteile:

finding out why a build failed is sometimes very annoying. scrolling a huge page of logs is not smooth (and maybe some better segmenting options there could be useful) we have a weekly recurring job that fails for linting reasons (but we still need it to run to get sonarQube coverage, idk if this is on us for bad implementation) but then who ever deployed last they get an email saying that the build failed. and we can only opt in or out from the whole thing and not just that type of builds.

Fast, free (for OSS) continuous integration testing

Kommentare: Ensuring that the master branch of my projects remains stable and of release quality, by only allowing changes that pass CI to be merged.

Vorteile:

Web interface is fast and responsive. Builds are quite fast. It's free for OSS. Quite good documentation (comprehensive). Supports several environments, including Macs (and now Windows too).

Nachteile:

Not so easy to determine exactly what you need to run (e.g. which packages to install, what to sudo). A simulator/interactive environment for testing would be nice!

Not really sure what I'm doing still

Vorteile:

Travis CI is great when it works. I can develop, pass my local tests, then push to github, etc and Travis CI will make sure that my tests pass on a variety of different virtual machines. That is great. I also like the rainbow flags.

Nachteile:

I am perpetually confused when things break. On the good side there is fairly extensive documentation. However, a lot of times it is still chewing gum and duct tape. Big sticking point is interacting with services like coverage and code quality tools. I also never quite figured out what the deal was when they switched from Travis.org for open source accounts to travis.com. The transition was super janky, and I still have projects that I think are in the old system, despite trying to bulk transfer all of them.

Recommendation

Vorteile:

It's easy to use and configure and also a nice user experience.

Nachteile:

It's expensive in comparison to other solutions

favorite auto builder

Kommentare: it auto builds my software's making it easy and convenient for me to start testing immediately

Vorteile:

its easy to use, super fast and automated

Nachteile:

i failed to understand the documentation first time i started using it

Easy with limit

Kommentare: Globally is good but it's necessary to use two CI software.

Vorteile:

Easy to run and find some example No breaking change

Nachteile:

1 hour limit for iOS build. You must use two software ... Not a lot of new feature

Review

Vorteile:

I love the ease of integration with CI workflow for github and heroku

Nachteile:

Slow to pick up hooks from builds on occasion

Travis meets my needs

Kommentare: We use to travis to build our API and deploy it. Various websites as well.
Have used the product to integrate with Veracode.

Vorteile:

Travis integrates with github, and slack.

Nachteile:

Sometimes the scripting of yaml files is agonizing.