1. In staging system, Make sure that the authentication profile: DMReleaseAdmin is configured properly with the correct username/password with which you are logging in to your orchestrator
2. In Orchestrator system,Make sure that the authentication profile: DMAppAdmin is configured properly with the correct username/password with which you are logging in to your candidate systems(DEV,QA,Staging,Prod)
2. Make sure you have DEV repository present in your staging system also , with the same name as that of in Orchestrator
Note: Once the RAP is successfully published to DEV repository, Deploy step in staging will pick the RAP from DEV repo and deploys in to the staging system.
If you still face any issues deploying in to the staging, Please let us know and send the complete log file.
Deployment Manager supports file system repositories.There is no restriction on it.
The contents in the product file should be imported to the staging system once the deploy step is staging is successfully completed. Please check whether the contents of the product file is imported in to staging system.
Could anyone explain me what is the use of "Deploy an existing artifact" option during CICD process. My understanding is once we do the "Generate new artifact" deployment, Zip file will get stored into repository and the same zip file will move into the different environment.
Once we so this what is the use of "Deploy an existing artifact" option anyways only the file that got stored into repository will show in dropdown.
A previous build artifact was successfully created, but failed to deploy to other systems. You could manually kick off a build and choose the existing artifact and move that along. If you are having connectivity problems with QA, for example, you might need to try again and again. Although there's no harm in just creating a new artifact, using the existing artifact might help keep your repo cleaner.
An artifact has been manually created and added to the repository that needs to be pushed through the pipeline. I can imagine this could be useful with an emergency bug fix process if they current state of development is not ready to be published and a custom Product rule is needed to ship only the exact rules and data needed. I'm not sure I'd recommend this, but this feature makes it an option.