Argo workflows
Learn how to integrate Debricked with Argo Workflows.
Last updated
Was this helpful?
Learn how to integrate Debricked with Argo Workflows.
Last updated
Was this helpful?
Argo Workflows is supported by using our "debricked/debricked-scan Docker" image.
Our Argo workflows integration support the same options as our Bitbucket integration, read more about the options here https://bitbucket.org/debricked/debricked-scan
Start by . Copy the token so that you can use it in the next step.
Depending on what package manager you are using there are different step setups.
In order to analyze all dependencies in your project, their versions, and relations, files containing the resolved dependency trees should be created prior to scanning. The file creation depends on the package manager used. Debricked tries to generate the lacking files, which can negatively affect speed and accuracy.
Example 1: If is used in your project, you will have a "package.json" file, but in order to scan all your dependencies, Debricked requires either "package-lock.json" or "yarn.lock" as well.
Example 2: If is used in your project, you will have a "pom.xml" file, but in order to resolve all your dependencies, Debricked requires 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 to your ".circleci/config.yml" file (if the file does not exist, create one):
Consider secrets instead of parameter binding with -p.