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
We have been using Dependency Track for a while now.
Unfortunately, the number of projects is increasing a lot because we store MR commits and tags.
I would like to tidy up our DT backend a bit and have stumbled across the "active" attribute.
My question would be, what exactly does setting projects to inactive do?
I could read in MR that projects disappear from the statistics.
Also, should certain tasks no longer be executed?
Does this mean that inactive projects are no longer analyzed?
Could you create projects with "inactive" and run them manually?
Are there other people who have several versions of their projects in Dependency Track? I would be interested to know how you handle this.
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
-
Hello dear community,
We have been using Dependency Track for a while now.
Unfortunately, the number of projects is increasing a lot because we store MR commits and tags.
I would like to tidy up our DT backend a bit and have stumbled across the "active" attribute.
My question would be, what exactly does setting projects to inactive do?
I could read in MR that projects disappear from the statistics.
Also, should certain tasks no longer be executed?
Does this mean that inactive projects are no longer analyzed?
Could you create projects with "inactive" and run them manually?
Are there other people who have several versions of their projects in Dependency Track? I would be interested to know how you handle this.
Beta Was this translation helpful? Give feedback.
All reactions