Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.0.4
-
None
-
6
-
Severity 2 - Major
-
5
-
Description
Issue Summary
Deleting a deployment project/environment that is consuming an artifact from globalStorage will leave the artifact orphaned on the disk and will be never deleted by the expiry.
Steps to Reproduce
- Create build plan B that shares an artifact.
- Create a deployment project DP that consumes the artifact of B and deploy the first build result to a stage in DP.
- Build B 4 times and trigger the expiry ( assuming that the expiry will keep last 3 build results and 2 deployments. This will move the first artifact of B to the globalStorage/artifactID).
- Delete DP
Expected Results
The artifact in globalStorage/artifactID is deleted when the deployment is deleted or during expiry.
Actual Results
The artifact in globalStorage/artifactID is never deleted.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Attachments
Issue Links
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...