Can i avoid artefacts being stored in the globalStorage Directory by defining them as "job artefacts" instead of "shared artefacts"?
The artifacts are moved to global storage when they are attached to deployments and the build result tied to a version is deleted. The only way of avoiding that is not deleting the builds.
Job artifacts are not moved to global storage.
Is the attachment to a deployment project the point or the linkage with a version/release which is deployed by the project? Our bamboo delete older artifacts not the build results or logs. It would be ok if artifacts getting stored when they are connected to a specific release of a deployment projekt. But it would be bad if they getting stored with every expiry only because they are connected to a deployment project. We have to delete the artifacts because we running out of diskspace.
@Przemyslaw Bruski
It looks like you're new here. Sign in or register to get started.
