BuildKite is supported by using our debricked/debricked-scan
Our BuildKite integration support the same options as our Bitbucket integration, read more about the options here: https://bitbucket.org/debricked/debricked-scan
Configure Debricked token
Start by generating an access token. Copy the token, so that you can use it in the next step.
Create a pipeline secret, that is called DEBRICKED_TOKEN and has the previously created access token as its value.
Configure BuildKite
If you do not have a BuildKite pipeline set up for your repository, make sure to create one.
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.
- Add the template to your .circleci/config.yml file (if the file doesn't exist, create one)
- Commit your changes to .buildkite/pipeline.yml and watch the CI run!