- The project structure in Dependency Track will always be two levels deep:
- a _root_ project bearing the name of the GitLab project namespace,
- it will be created as a [collection project](https://docs.dependencytrack.org/usage/collection-projects/) aggregating all its direct children (requires a Dependency Track version higher than 4.13.0)
-`DEPTRACK_PARENT_COLLECTION_LOGIC` will set for which children statistics will be collected or disable the collection
-`DEPTRACK_PARENT_COLLECTION_LOGIC_TAG` for the tag to match for if the `DEPTRACK_PARENT_COLLECTION_LOGIC` is set to `TAG`
- and _leaf_ projects (hosting SBOM files) bearing the full path of the GitLab project as a name, suffixed with the
SBOM file prefix and with project version matching either the Git branch name or the Git tag name (depending on the
kind of pipeline that originated the SBOM file).
@@ -166,12 +169,14 @@ Examples:
The Dependency Track template uses the following configuration.
| Input / Variable | Description | Default value |
| `project-path` / `DEPTRACK_PROJECT_PATH` | Dependency Track target project path to publish SBOM files to | `$CI_PROJECT_NAMESPACE//$CI_PROJECT_PATH-{file_prefix}@$CI_COMMIT_REF_NAME` |
| `path-separator` / `DEPTRACK_PATH_SEPARATOR` | Separator to use in project path | `//` |
| `parent-collection-logic`\ `DEPTRACK_PARENT_COLLECTION_LOGIC` | Set up how the parent aggregates its direct children (ALL: all, TAG: with tag matching, LATEST: flagged as latest, NONE: disable) | `ALL` |
| `parent-collection-logic-tag`\ `DEPTRACK_PARENT_COLLECTION_LOGIC_TAG` | Tag for aggregation parent-collection-logic is set to TAG | _none_ |
| `tags` / `DEPTRACK_TAGS` | Tags to attach to project (comma separeted list) | _none_ |