Best posts made by MaxCascone

I think I can get close enough, without a lot of complexity, by using the retention rules, and setting them fairly tight since it's a dev feed and these packages are meant to be transient.

We don't have a package promotion process right now, although it's on my roadmap. These rules may have to be revisited when i implement that.

Right now I've got it set for:

• Delete unused versions not requested in last 30 days.

We are not great at deleting old branches, so this might actually be better than a branch-delete trigger. And if someone comes along and needs an old branch build, they can just rebuild it.

We don't really use the connector feature for our own feeds (or any), so i think this will do it.

I got a little confused at the combination of "keep only last 5 versions" plus the 30-day window. From what i've read in the docs, all conditions must pass for the item to be deleted. How do i set up, "keep only the last 5 versions, but when nothing has been requested for 30 days, delete them all"?

This solution has the benefit of simplicity and native functionality. I don't have to write a hacky, multi-tool process to manage it.

Thanks Alana, I continue to be impressed with your and Inedo's responses to these issues!

We are not on v2022 yet, we are on the latest v6 as of a few weeks ago, but now we have a real reason to do it!

Thanks again!
Max

Thanks for the insight into your process on this. It's interesting.
For our part, I put everything I can on Confluence. I probably like Confluence as much as I hate Sharepoint and OneNote. (At least with OneNote I can actually create a document successfully.)

Flow charts help a lot, which are super easy to create and maintain with the Draw.io integration into Confluence.

I like confluence for its deep-linking into Jira as well.

Yuck, sharepoint?

I hear you; SOPs tend to wither and gather dust as the processes evolve, though, in my experience. That's why, while we get some real-world use of the manual promotion and versioning processes, in the hope that repeatable, reliable patterns emerge that we can then automate, we want to remind people in-flight what the process is supposed to be, so they don't make mistakes.

thanks for the reply!