We gave 'Deploy existing artifact' option in earlier versions to make it easier for requirement of pipeline which needs more than 4 environments(DM did not support more than 4 environments in pipeline before 5 version). So that they can split the pipeline and use this feature for extended pipeline.
But in DM 5.X version there is an option to have more than 4 environments. So did not find any use case to give this feature.
We have separate pipelines. One Pipeline to deploy code from Dev to UTest and PreProd and other pipeline which does Prod deployments. We have this setup in DM 8.4 and wanted to be the same in DM 5.2.
We do PROD deployment once in every month. We do deployments from Dev to UTest and PreProd every other day. So, we want the pipeline to run until PreProd and publish the RAP to PROD folder in Nexus repository . At this point, we do not want to abort the pipeline to start a new deployment. We want the pipeline cycle to end at PrePROD and use separate pipeline for PROD deployment.
For any reason, if Sprint A Prod deployment was put on hold and Sprint B starts, there is no way to deploy the Sprint A code just to PROD unless entire pipeline cycle is executed. Sprint A Data instances might get modified from Sprint B and we don't want the build the product again.
Also, I don't want to deploy all production ready artifacts. I just want to deploy the artifact that I use for that current deployment.
@ChinmayaHegde I like how things are implemented in the multispeed-deployment process. It would resolve most of the issues. (Build for Change :-))
We use the same pipeline to deploy multiple products. Is there a way that superseded deployments are resolved only for the builds that match the product name of the newer deployment ?? Would be a nice enhancement if not.
Also, is there a timeline for the next Deployment manager release version along with features? Would be helpful if we know what's coming next.