It’s time for the final part of the Travis CI Community Survey results. Check out part 1 and part 2 of the blog posts to learn about the most common languages, platforms, deployment targets and more. Today, we’ll be going over popular features and the improvements you requested.
Interested in knowing what trends we found in the Travis CI Community Survey? Keep reading to learn about the most popular deployment targets, common sources of troubleshooting information and your feedback on the Travis CI UI/UX.
We’re delighted to share the insights from the Travis CI Community Survey launched at the end of last year. We’ve been so eager to learn from you and share the results to help us all better understand the community that makes up Travis CI.
In total, we have received almost 900 responses! To break it down:
440 use Travis CI in open source projects (whereas 56% also test private projects)
At Travis CI, we are committed to building the best Continuous Integration and Deployment solution for your projects. This ultimately means building the best service for everyone: users, teams, and the community. Today, we are happy to share a first look at our upcoming themes for this year.
When building our roadmap, or planning any feature with our team, we always consider three key questions:
Does it make Travis CI easier to use?
Does it improve build performance?
Does it improve the quality for customers and the community?
We believe what we’ve planned for this year will delight you, all our users, and the community as a whole.
Hey folks! We’ve just launched an Xcode 10.2 beta 2 (Build 10P91b) build environment!
Add the following to your .travis.yml to try out the Xcode 10.2 beta:
We’re also excited to announce that our Xcode 10.2 beta builds are the first ones running
Because this is a beta release, you may have unexpected issues or build failures when
using this environment. Please join us on the Travis CI Community
forums to discuss these issues and get help from us and your fellow developers!
As of today, January 31st, 2019, GitHub will stop sending events for repositories connected via their Legacy Services Integration. You’ll find more information about this on the GitHub Developer blog .
After this deprecation, Travis CI will continue building and testing your repositories as usual.
When we started working on a Continuous Integration solution back in 2011, it was hard to imagine what Travis CI would become. Years later, we’re still continuously working to make our community and the tech industry better and stronger. Today we are excited to announce that Travis CI has been acquired by Idera, Inc. Idera is the parent company of many software productivity tools and will support us in delivering quality software to all of you, our users.
Grown out of the open source community, Travis CI became the leading CI solution and we now provide enhanced features, performance, and support to projects and teams of all sizes. We are proud to serve more than 700,000 people worldwide to build and test software applications. Our customers include IBM, Schibsted, and Zendesk, amongst many others. Together with Idera, we want to expand on this success and help many more people build better software faster.
We’re excited to launch the Travis CI Community Survey
How do you use Continuous Integration? What do you love about Travis CI? How can we improve your experience? These are questions that we ask ourselves frequently. Today, we’re asking what you think in the 2018 Travis CI Community Survey.
We’re so excited to get your feedback! It will give us a chance to learn about (and from!) you all, the amazing Travis CI Community. The feedback we collect will help us understand your needs and will impact the way we build and improve Travis CI in 2019.