Travis CI Blog

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. CI/CD pipeline security is a…

Increasingly, software imposes security requirements on developers. As software is built using multiple libraries or utilities, developers introduce a lot of dependencies into the final product that they actually do…

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.

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 development methods using the DevOps…

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 used for building, testing,…

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 signing the software by…

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…

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…