• More performant Builds on Travis CI

    Hopefully, 2020 has started well for you! With the new year, new challenges arise in software development: Machine Learning, Artificial Intelligence, Big Data, just to name a few. What do all of these have in common? Working in these areas requires a lot more resources during development, testing, and production.

    As a developer, you’re on top of it to deliver products that are enhanced with new technologies to deliver more value to your users and customers. With the increasing number of new technologies becoming an integral part of your applications, you also need to make sure that they’re well tested and behave as expected.

    We’re now providing larger instance types on travis-ci.com so that you can leverage the additional computing power to also incorporate more elaborate testing scenarios in your testing workflow.

    Does that sound interesting to you? Get in touch with us via sales@travis-ci.com and we’ll get you set up with a trial right away.

    Continue


  • Database Maintenance on Saturday, 1st of February 2020

    On Saturday, February 1st, travis-ci.com will be down for planned maintenance for around 2 hours, starting at 1 pm UTC and ending by 3 pm UTC. We will be performing some necessary database maintenance on the platform.

    Continue


  • Open call for Rails Girls Summer of Code projects and mentors

    How we work to improve diversity in tech with Rails Girls Summer of Code

    Community is at the focus of everything we do at Travis CI. That’s why we’re proud to be running and sponsoring Rails Girls Summer of Code, a fellowship program administered by a non-profit initiative run by Travis CI, the Travis Foundation.

    RGSoC supports female and non-binary coders around the world by offering scholarships to work on open source projects for three months, from July to September.

    This breaks down the financial barriers that all too often prevent individuals from underrepresented groups entering a career in tech. Student teams are supported by mentors, coaches and experienced programmers that help develop their skills and confidence in coding.

    Continue


  • Database Maintenance on travis-ci.org on Sunday, 15th December 2019

    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.

    The maintenance process will be similar to the maintenance last week on travis-ci.com.

    Continue


  • 2019 Travis CI Community Survey

    With the end of the year approaching, we’re excited to launch the 2019 Travis CI Community Survey.

    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!

    Take the survey.

    Continue


  • Database Maintenance on Saturday, 7th December 2019

    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.

    Continue


  • Build your open source projects on IBM Power and IBM Z CPU architecture

    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.

    Continue


  • Share and import yaml snippets to your build configuration

    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.

    Import shared build configurations at Travis CI

    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.

    Continue


  • Keeping Your Data Secure with Our First Bug Bounty Program with HackerOne

    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.

    Continue


  • Build Config Validation now in beta

    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 certain features.

    You can enable this feature using the repository setting “Build config validation” in the Travis CI UI, or by specifying the version in your .travis.yml file:

    version: ~> 1.0
    

    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:

    Continue