How does package caching work exactly?


(Matt Ford) #1

Hi,

We recently tried to deploy a product to a new server using the last release used. However, it failed as the packages were removed (see below)

Now the packages are held in an instance of MyGet and they were removed, but I expected it to not find the package and just carry on with the cache, not error.

We’re on 2018.9.6 of an on-prem instance.

Is this a bug or have I misunderstood?

Thanks

/Matt


(Henrik Andersson) #3

Hi Matthew,

Thanks for getting in touch and I’m sorry you are having these issues.

The package cache for external feeds are stored (by default) for 20 days (and the file hasn’t been accessed for the last 3 hours of the scheduled cleaner task run), so in this case I assume that the package used here had been removed from the package cache unfortunately.

You can change the number of days packages from external feeds are kept in the package cache by using the Octopus.Server.exe configure --cachePackages <DaysToKeepPackagesInCache> command.

My sincere apologies for the inconvenience caused by this.

Thank you and best regards,
Henrik


(Matt Ford) #4

Sorry for the delay Henrik. Thanks for the reply and no apologies needed as it’s my misunderstanding :slight_smile: