Travis CI

Learn how to integrate Debricked with Travis CI.

You can integrate your Travis CI pipeline with Debricked by using our debricked/debricked-scan Docker image. Just like our other CI integrations it just takes a few minutes to set up!

Configure Debricked token

Start by generating an access token. Copy the token to use in the next step.

Set your DEBRICKED_TOKEN variable by going to your repository, click the top button "More options" -> "settings" and go the section Environment Variables. Use the access token created in the previous step. Be sure to disable the Show value in build log button, so you don't expose your login credentials to the world

Configure Travis CI Workflow

Depending on what package manager you are using there are different step setups.

In order for us to analyze all dependencies in your project, their versions, and relations, files containing the resolved dependency trees have to be created prior to scanning. Those depend on the package manager used. If files are lacking we try to generate them on our side, which can negatively affect speed and accuracy.

Example 1: If npm is used in your project you will have a package.json file, but in order for us to scan all your dependencies we need either package-lock.json or yarn.lock as well.

Example 2: If Maven is used in your project you will have a pom.xml file, but in order for us to resolve all your dependencies we need a second file, as Maven does not offer a lock file system. Instead, Maven dependency:tree plugin can be used to create a file called .debricked-maven-dependencies.tgf.

  1. Choose one of the following templates and add it to your travis.yml file. If the file doesn't exist, create one:

  1. Commit your changes on the.travis.yml file and watch the CI run!

Last updated