Rob Erez on 21 Feb, 2018 11:33 PM
It's funny that you should bring this up as we have recently just begun to think about how Automatic Release Creation might work for external repositories. Check out some of our early thoughts on how we think that might work and let me know what you think. There is also a uservoice ticket describing the idea that I would suggest you add your vote and thoughts to. The more interest we get from users on any particular issue the higher we are able to prioritize it. Cheers,
Hi Rob, yeah, the timing not a coincidence :) I've seen you guys have mentioned in release notes some changes to Feeds API (which we use for several scenarios) related to future changes to Feeds functionality. So I thought that's a good moment to remind about autodeployments from external feeds :) Glad to hear you're thinking about it.
Another improvement, which would be good to hear of is whether you're thinking about being able to configure retention policies to external feeds.
Rob Erez on 23 Feb, 2018 04:50 AM
Good to hear that someone reads our release notes :)
I'm definitely keen to get the ARC set up for external feeds so trying to work out how it fits into our short term priorities. Watch this space.
At the moment we don't have any plans to configure retention policies for external feeds. What would be the typical scenario you would be hoping this would solve?
Well, we cannot use built-in nuget feed due to the amount of packages we have, but we do need to clean-up unused packages. So we had to implement a script which deletes all nuget packages (from specific nuget feeds), not bound to any Octopus release.
Oh, but we also had to implement our own retention policy for nuget releases. We keep releases in accordance to our (yet very simple) policy - keep releases which either currently deployed somewhere (to some environment), or which are newer than X days, or "immune" because they were deployed to specific environment (e.g. Production).
Rob Erez on 09 Mar, 2018 04:40 AM
That sounds like an interesting scenario. I can understand why you may want Octopus to be responsible for cleaning up external repositories. I'd advise that you perhaps create a https://octopusdeploy.uservoice.com ticket outlining this idea. That will help us keep track of it and asses its viability alongside other features.
Thanks for getting in touch, I'm certainly trying to push for the external feed ARC work so keep your ear to the ground
Oh, there is a mistake. Please read "Oh, but we also had to implement our own retention policy for nuget releases." as "Oh, but we also had to implement our own retention policy for OCTOPUS releases." The thing is, Octopus Releases retention policy is not flexible enough to use. So we have implemented script, which deletes both Octopus Releases and Nuget packages. According to some rules.