On Sunday, December 15th travis-ci.org will be down for planned maintenance for about 2 hours starting at 1 pm UTC and ending by 3 pm UTC. We will be performing some necessary database maintenance on the platform.
Your feedback last year has been invaluable and we look forward to learning more about your experience using Travis CI this year. The insights we obtain will help us understand your needs and will impact the way we build and improve Travis CI in 2020.
What has been working well? What should we improve? What should we focus on next year? Tell us about your experience and help us build a better product!
On Saturday, December 7th travis-ci.com will be down for planned maintenance for about 2 hours starting at 1 pm UTC and ending by 3 pm UTC. We will be performing some necessary database maintenance on the platform.
Last month, we introduced the capability to build open source software for multiple CPU architectures. Today, we’re excited to extend that capability beyond arm64 and amd64 to using the same Travis CI infrastructure to seamlessly build on IBM Power and IBM Z architectures!
Thanks to the partnership with the Canonical, IBM Power and IBM Z teams we can share this awesome feature with all of you in this early release.
At Travis CI, the main source of configuration for your builds has always been
the .travis.yml file stored in your repository, and it can be customized by
including configuration when triggering builds with the API.
Today we are happy to announce the new beta feature Build Configuration Imports that
allows you to import shared YAML build config parts to your .travis.yml file or
config included in API build requests.
Build Config Imports let you save time by defining reusable configuration
snippets, so that you can fetch commonly used recipes with a single import
line, and standarize your build and deploy configuration across repositories.
Keeping your information safe is a top priority at Travis CI. We are constantly working on solutions to keep your data secure and we want you to know that the information you share while using Travis CI is protected.
That’s why today, we’re excited to launch the Travis CI Bug Bounty Program with HackerOne.
We are excited to announce the new Build Config Validation feature. It is now
in beta, and available for you to activate.
When active, the build config validation
feature will validate and normalize any incoming build config sources,
your .travis.yml file and configs from build requests created via API.
We are hoping to give you more clarity about the build config format and
ultimately a better experience when activating a repository and enabling
You can enable this feature using the repository setting “Build config
validation” in the Travis CI UI, or by specifying the version in your
The validation process produces validation messages that you can review on the
respective build’s “View Config” tab in the Travis CI UI. This gives you direct
insights into how your build config has been processed, what issues Travis CI
might have found, and how to resolve them:
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.