Say you have an open source Python project or package you are maintaining. You probably want to test it on the major Python versions that are currently in wide use. You definitely should. In some cases you might also need to test it on different operating systems. I’ll discuss both scenarios, and suggest a way to do just that, in this post.
You have been asking us where to get Travis CI merch for a long time. As a distributed team, it’s been challenging for us to respond to your swag requests properly. We’re ready to share that we opened a Travis CI Online Store to get you your favorite t-shirts and stickers quickly. 🎉
Go to shop.travis-ci.com to order Travis CI t-shirts & stickers!
At Travis CI, we’ve partnered with the snapcraft team to improve the development experience while building, releasing and installing snaps.
Since the snapcraft summit two weeks ago, we’ve been working closely with developers of many programming languages so we can make their snaps available for you to use on Travis CI at build time.
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.
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.
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: xenialthe 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.
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.
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.
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.
Hey folks! We’ve just launched an Xcode 10.2 GM (Build 10E125) build environment!
Add the following to your
.travis.ymlto use Xcode 10.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.