You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, Im just getting started with trying out dependencytrack! Everything looks smooth so far however Im unable find clear documentation on how I should structure my projects (parent/subproject?).
Should I create a parent project named system-x which acts like a group for all applications belonging to system-x?
Should I submitt a single BOM for the application + container or submit multiple?
Can the parent project give some kind of summary? Seems to me like the parent just shows 0 components etc.
Also, is there a recommended way to keep track of what is actually deployed in production? Maybe something like keeping a version for each project called "production" which you would update each time you deploy something new?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, Im just getting started with trying out dependencytrack! Everything looks smooth so far however Im unable find clear documentation on how I should structure my projects (parent/subproject?).
Also, is there a recommended way to keep track of what is actually deployed in production? Maybe something like keeping a version for each project called "production" which you would update each time you deploy something new?
Thanks in advance for any thoughts!
Beta Was this translation helpful? Give feedback.
All reactions