• Case Study: How the IBM Cloud Kubernetes Service team uses Travis CI

    Many challenges face today’s software development teams. They must improve productivity, address external security threats, and adopt new technologies to improve uptime and scalability. Travis CI enabled the Cloud Kubernetes Service team at IBM to address all of these issues. Leveraging Travis CI as part of their DevOps culture change, IBMers decreased deployment times from weeks to hours, improved security, and were able to build their applications at scale.

    Michel McKay, the DevOps lead for the IBM Cloud Kubernetes Service team, was able to meet with us and share his insights into adopting Travis CI and how it has benefited his work.


  • Setting up a CI/CD Process on GitHub with Travis CI

    Setting Up a CI/CD Process on GitHub

    You’ve created something amazing. You’ve published on GitHub. People are downloading, using, forking, and contributing. The community is thrilled. But are you ready for the oncoming glut of Pull Requests?

    Continuous Integration/Continuous Delivery (“CI/CD”), two terms so frequently mentioned together they’ve been fused into one concept, refers to the automation of such repetitive tasks as testing, building, and deploying software. Over time, it has become an invaluable tool in maintaining a productive and functional team.


  • Ubuntu Xenial 16.04 as the default Travis CI build environment

    Xenial as the default Travis CI build environment is coming up next week, starting incrementally on Tuesday April 23rd, 2019.

    Since Ubuntu 14.04 reaches End of Life on April 30th, 2019, we’ll be gradually setting the default distribution for builds to Linux, Ubuntu Xenial 16.04.

    We plan to make dist: xenial the default for all builds by the beginning of May 2019, and we’ll make sure to let you all know here and in our changelog as soon as the default build environment switch is done.


  • Incident review for slow booting Linux builds outage

    Two weeks ago, on Wednesday, March 27th through the 28th, we had a major outage affecting both of our platforms, travis-ci.com and travis-ci.org. For about 20 hours, all builds on our Linux and Windows infrastructures were delayed.

    We are deeply sorry for the inconvenience this has caused you, and we want to let you know what we’ve found and the measures we’ve taken to improve the reliability of our service.


  • Travis CI Insights: better build metrics

    We are happy to announce Insights for your builds. Insights will bring you more intuitive display of how you and your team use Travis CI.

    Development is often data-driven, and your CI should be no exception to that. Starting today, you will get more information about your Travis CI usage, from wait times to overall build status results.


  • Travis CI Community Survey Results 2018 - Part 3 of 3

    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.


  • Xcode 10.2 GM is now available!

    Hey folks! We’ve just launched an Xcode 10.2 GM (Build 10E125) build environment!

    Add the following to your .travis.yml to use Xcode 10.2:

    osx_image: xcode10.2

    Xcode 10.2 builds are the first ones running macOS Mojave!.

    If you were using the Xcode 10.2 beta image before, you will automatically start using the GM image now. No change to your configuration is needed.


  • Travis CI Community Survey Results 2018 - Part 2 of 3

    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.

    In the first part of this blog post, you can find information on the most popular programming languages and platforms.

    Make sure to join us in the Community Forum to discuss the results of the Travis CI Community Survey 2018.


  • Travis CI Community Survey Results 2018 - Part 1 of 3

    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)
    • 295 mainly test private projects
    • 10 represent large enterprises testing on-prem with Travis CI Enterprise
    • 60 are students on Travis CI Education
    • 30 are not using Travis CI
    • 30 don’t have experience with CI at all


  • What's in store for Travis CI in 2019

    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.