Retention policy is not applied to nuget package repository

Legacy Uncategorised
1

We have retention policy to keep 2 releases, and keep packages for 1 day.


But packages are not deleted



Retention task periodically (every 2 days) hangs with no output in log.

2

Hi Igor,

What version of the Octopus server / Tentacles are you currently running?

Are packages and files on the Tentacle being removed as per the retention policy when you do a deployment? (I can only see that the packages stored on the Octopus Server isn’t being removed.)

If the packages/files on the Tentacle aren’t being removed, could you please send through a full deployment log from one of the tasks where the retention policy should’ve been applied?

Thank you and warm regards,
Henrik Andersson

3

We use 2.5.10.567

Files on tentacles are removed correctly, problem only with package repository. Here is logs from 2 last retentions (the last failed, but previous was successful, and repository still contains old packages).


4

Hi,

The issue with the package repository has been fixed with the release of 2.5.12 that happened today.

Vanessa

5

Thanks, packages are deleted now. But there is another problem - packages for deployed releases are also deleted

screencast http://screencast.com/t/dQmiiwVx7

6

Hi,

I’ve created another GitHub issue to look into this

Vanessa

7

Hi Igor,

Those old developer words that everyone hates, “we can’t replicate this”.
Can we setup a screen sharing session to work this out:
https://octopusdeploy.acuityscheduling.com/schedule.php

Thanks
Vanessa

8

Hi,

Done.

9

Hi,

The problem comes again after updating to 2.6. Releases are not deleted, see screencast http://screencast.com/t/drofKXsS

10

Hi Igor,

Is the Aeroflot package used in any project that uses dynamic package IDs (e.g. using a variable to pick which package to use)?

If a package is used in a project that does use dynamic package IDs, we don’t delete that package.

Thank you and warm regards,

Henrik

11

Hi Henrik,

Thanks, its clear now.

Any chance that logic described in this comment would be implemented soon? https://github.com/OctopusDeploy/Issues/issues/1341#issuecomment-62865276

Are we the only ones that faced this problem? IMO there is a much common scenario to use dynamic Ids.

Maybe we are doing it wrong?

Igor Kudrin, CIO
Mindboxhttp://www.mindbox.ru/

От: Henrik Andersson <tender2+d1f4c9dea38941151f7a1127ad81ca324917ff2ff@tenderapp.commailto:tender2+d1f4c9dea38941151f7a1127ad81ca324917ff2ff@tenderapp.com>
Дата: среда, 14 января 2015 г., 4:55
Кому: Igor Kudrin <kudrin@mindbox.rumailto:kudrin@mindbox.ru>
Тема: Re: Retention policy is not applied to nuget package repository [Problems #26315]

12

Hi Igor,

I’m not sure which logic in that comment you mean? Are you referring to is there a release with 1.0.0 selected for that step? If not, delete the package.?

I’m not sure if you guys are the only ones who has run into this issue with the package retention policy, but we haven’t heard from any other users about it.

Thank you and warm regards,

Henrik

13

Hi Henrik,

Yeah, all described there. Delete all packages that were never deployed to any environment.

Currently we have to delete packages manually – I think it is unacceptable for commercial product.
Solution «we will delete no packages» for problem «we deleting all packages» looks a little bit strange.

The previous logic «delete all packages older than X days» was more acceptable, cause we at least was not facing packages eating all disk space like it happens now.

How are you using packages? Are you using one static package ID for all releases? I cant imagine scenario without variables in packages name.

Igor Kudrin, CIO
Mindboxhttp://www.mindbox.ru/

От: Henrik Andersson <tender2+d1f4c9dea38941151f7a1127ad81ca324917ff2ff@tenderapp.commailto:tender2+d1f4c9dea38941151f7a1127ad81ca324917ff2ff@tenderapp.com>
Дата: вторник, 20 января 2015 г., 4:45
Кому: Igor Kudrin <kudrin@mindbox.rumailto:kudrin@mindbox.ru>
Тема: Re: Retention policy is not applied to nuget package repository [Problems #26315]

14

Hi Igor,

Firstly, let me apologise for the troubles you are having with the package retention!

Secondly, the solution we came up with was a stepping stone in the path to a better over all package retention policy, we probably took it one step to far to ensure that packages that would be deployed wouldn’t be removed before they could be deployed.

Let me assure you that package retention policy is still very much on our radar of things that needs to be improved.

Thank you and warm regards,
Henrik