We would like to share with you that all Xcode 11 builds released by Apple up to now are available as build environments!
Between beta and GM updates six versions were released and we saved the most recent to you, get them while they’re hot!
You can run your tests on Xcode 11.0 (11A420a), Xcode 11.1 (11A1027) and Xcode 11.2 beta (11B41).
We’re excited to share that you can now test your open source software on multiple CPU architectures at Travis CI.
For the past few months, we’ve been working closely with the Travis CI community, the LXD team from Canonical, Arm and Packet.
Thanks to this partnership, Arm-based builds are now available to you, for free, for your open source projects. Arm-based builds are the first ones to use LXD powered containerization to run your builds.
If your public projects are targeted for Linux and Arm CPU Architecture, get started with Arm builds today!
Over the last few months, we have been rewriting the current codebase of
dpl, our deployment tooling, and the result
is a new major version: dpl v2.
Almost every line of code has been touched, code quality, test coverage and
test quality greatly improved, and many of the supported service providers and
volunteer contributors have been involved. We are excited about this huge
community effort to improve and modernize dpl and give you the best
The diff stat on the main pull request
for this work gives a vague impression of its extend:
Out of these ~16,000 lines, less than 7,000 are implementation code, the rest
is documentation, tests, etc.
Today, we are releasing dpl v2.0.0-alpha.1 as a developer preview release, and
would love for you to try it out.
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. 🎉
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.
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.