Need method of cleaning component versions that works well with Release Control Hot
Request cleanup of component versions based upon prefix of component name or based upon Release Control request ID.
For those of us that utilize Serena Deployment Automation (SDA) with Serena Release Control (SRC) and perhaps even with Dimensions CM (aka Serena Release Vault), we need a different auto-clean utility in SDA.
In our process, we create a request in SRC and, depending on our process, this may trigger a build and the creation of new artifacts and a baseline in Dimensions CM. The baseline is named with the first part of the baseline name being the request ID from SRC. Using automatic import, this baseline is imported into a component in SDA. This component may have hundreds of component versions -- basically all work done within the same Dimensions product will end up in the same SDA component. However, the first portion of the baseline name easily identifies which request this baseline belongs with.
As the artifacts are deployed to DEV, then into TEST environments, problems may be found which cause code changes, new builds and new baselines -- all against the same request. Finally, the artifact is ready for deployment to production. At this point in time, we'd like to purge away all or most of the previous baselines that were part of this request. Unfortunately, SDA will not let us manually delete them because they were once deployed. We also cannot have them auto-cleaned because our version choices there are based only upon number of versions or number of days. In times when we may have a handful of requests in the air against the same component, this will not do.
We would like a bit more flexibility added to the auto-clean (or the manual cleanup). We'd like to be able to remove all but the last 1, 2, or 3 of the versions against a given SRC request.
It seems this may be desirable for anyone using SRC in conjunction with SDA.
Please login to view any attachments.
There are no user comments for this idea.