Support the archiving of non-active projects
From the following support topic http://help.octopusdeploy.com/discussions/questions/6809-archiving-projects
Octopus deploy does not currently support a model for archiving/unarchiving non-active or legacy projects.
The workarounds are permission-based or user-specific but not quite what I would like to see.
what I am suggesting is similar to Teamcity's archiving functionality. I have found this ability in TC to be useful in the 7+ years I have been using it where I have accumulated many different applications, some of which are no-longer in production, some which are in production but in maintenance mode only and those in active ongoing development.
For the most part I only require the latter type of projects and the rest are archived.
With 30+ projects in active development, this helps reduce the noise levels and I would find it of similar benefit to manage OD in the same way for all our developers (so needs to be server rather than user level)
Scott
shared this idea
-
Anonymous
commented
agreed, I'm used to archiving in Teamcity and would like to see this in octopus as well to be able to retain history of past deployments
-
Steve Tyler
commented
This would be a great feature in my environment, where retention policies aren't used because the historical deployment data is infinitely more valuable to keep than the packages, but we can't remove the packages without deleting a release and losing all that information.
-
Chad Ruppert
commented
Actually, I would love this too. We do a lot of smaller projects shorter lived projects, and still would like to deploy many of them via octopus. Because every one of them runs against our "thing count" in licensing, and budgetary concerns prohibit larger plans, we don't. Technically we could if we were willing to delete all the historical data and anything not from a template in the deployments at the end of each project, but we don't.
Teams on those projects end up using the azure deploy from git for those because while not great, it gets the job done and doesn't cost me extra. I'd obviously prefer to use octopus, because the experience is almost universally better for our team - for now.
-
Dan S
commented
Love this idea, and was searching for something similar today. It would be really handy to archive projects that are no longer in development or that have moved elsewhere, while retaining deployment pipeline setup in case we need to recreate it at a later date.
While I'm aware that exporting my entire configuration could do something similar, I am also keen to hold onto the old deployment details: they don't take up much room, and for me it is more about hiding these old projects by default. Allows me as administrator of Octopus to clean up older or out of date projects without losing any data.