Travis CI Blog

 

CI/CD Security: Best Practices

Software development often consists of confidential information and code sequences that could put companies in a vulnerable position if leaked into the hands of competitors....

SVN and Perforce CI/CD Options

Travis CI’s SVN and Perforce CI/CD options enable developers to benefit from the security, storage, and automation features that our software has to offer.

CI/CD Pipeline: A Complete Guide

What is continuous integration (CI) and continuous deployment (CD)? Why has this method for delivering updates to software become the hallmark of advanced, modern software...

Improved CI/CD Build Job Log Security

The CI/CD (Continuous Integration & Deployment) tools are a widely adopted part of automated delivery processes in the software development industry. Tools like Travis CI are...

Sign your software with Travis CI

Software Supply Chain security is the act of securing the components, activities, and practices involved in creating and deploying software. One of these practices is digitally...

Deploying with Surge.sh

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

Build Imports in Travis

Sometimes you need a really dynamic configuration when setting up your pipeline. With imported configs, those configs can themselves include other configs, making this feature...