• 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.