Is there an overall strategy for how to manage build configurations at their "end of life"? The scenario is as follows:
I have a number of build configurations created to build the release branch of a project.
The release branch is no longer in active development. Newer release branches exist.
Artifacts from these builds should be archived for historical reasons.
The list of changes and the build log for these builds should also be preserved for historical reasons.
There are a number of issues in the Issue Tracker related to the management of build configurations that reach a natural state of deprecation:
TW-4151: Ability to preserve build history for a build configuration copy
TW-5543: Allow moving build configurations between projects
TW-5697: Add the ability to move build configurations between projects.
Presumably these could be used to create an "Archived" project that would hold these builds.
TW-3396: Confusing Paused build configuration state: not visible on My Changes view (To avoid confusion and make the product more user-friedly, let's rename Pause/Activate to Disable/Enable.
This issue talks about creating an additional categorization for builds as "Disabled" or "Inactive".
Finally, this issue:
TW-5161: Allow to archive projects
Seems to be the only one I can find to address this entire use case from a high level so I'm curious if there has been some internal discussion regarding this type of functionality. I think supporting this type of "Archiving" will require changes in a lot of places, for example:
Configuring the visibility of projects based on their categorization
Configuring access roles for users
How artifacts are stored. Perhaps creating an "archives" section within the artifacts folder?
Being able to preserve not only artifacts for old builds but build messages as well