• Deploying with Surge.sh

    Deploy to Surge with Travis

    Got some static files? Travis CI can deploy your static files to Surge.sh after a successful build. Builds triggered from Pull Requests will never trigger a deploy, let’s see how we can make this happen.


  • Complex Build Commands

    Complex Build Commands (1)

    Sometimes if you have a complex build environment that is hard to configure in the .travis.yml, consider moving the steps into a separate shell script. The script can be a part of your repository and can easily be called from the .travis.yml.


  • Travis CI Now Introduces Changes in Job Logs Availability

    Job Logs

    Travis CI job logs provide important information on executing specific jobs in a build. In addition, build job logs contain supplementary information, such as environment variables names and values, as well as custom debug outputs defined by the users. These debug outputs and unencrypted variables may hold vulnerable secrets (credentials, tokens). As a result, running builds in public repositories could lead to unintended and overlooked exposure of vulnerable information. To minimize risks, Travis CI introduces limits on how long and for whom the job logs will be available. These limits are configurable.


  • Use your own Hashicorp Vault instance with Travis CI

    Use your own Hashicorp Vault instance

    Don’t trust Travis CI with all your secrets needed for your pipeline, at least not too much. If you prefer to manage secrets needed for CI/CD processes in a central Key Management System (KMS), e.g. to be able to rotate them quickly rather than providing secure environment variables to the CI/CD tool, you can now easily connect Travis CI with Hashicorp Vault.


  • Conditional Builds, Stages and Jobs

    Conditional Builds, Stages and Jobs

    Sometimes you need to filter out and reject builds, stages and jobs by specifying conditions in your build configuration (your .travis.yml file). With conditionals, you can do that and more, let’s explore the full functionalities of Conditional Builds.


  • Ubuntu Jammy Jellyfish 22.04 is available!

  • Travis CI Build Explorer

    Build Config Explorer

    Ever want to know where you went wrong when configuring your .travis.yml file? You should try Travis CI Build Explorer. Travis CI build config format is formally specified using a JSON Schema. Travis CI uses this specification to normalize and validate build configs, let’s do a sample.


  • Travis Workspaces


    Workspaces allow jobs within a build to share files. They are useful when you want to use build artifacts from a previous job; for example, you create a cache that can be used in multiple jobs later.


  • Doing Certificates with Smallstep & Travis

    Do people still use X 509 Certificates

    You may know something called the ACME protocol for automated certificate management has seen vast adoption in the Web PKI since its inception in 2016. While initially conceived for usage on the public web, the protocol is also well-suited for usage on internal networks, e.g. infranets, infrachats at Colleges, etc. Let’s lerarn more about Smallstep.


  • Get started with Google Cloud SDK and Travis fast

    How to get started with Google Cloud SDK fast

    In the spirit of being fast, this tutorial will be as fast as the implementation and usage itself. Let’s get to it, running Google Cloud SDK, Docker and Kubectl. Let’s get started.