...
- Admin creates a release directory in “DevOps Repository Manager”.
- Developer uploads the applicable export.xml file to the “DevOps Repository Manager” directory with a standard naming pattern.
DevOps detects that there is an export.xml in that release directory and the automated scripts invoke silent migration utility to create export.zip file and import.xml in the same DevOps directory.
Note It is recommended that you set up an email notifications notification in Jenkins to receive an email in case of success or failure of a deployment. Developer reviews the export.zip to verify and ensure that no objects are missing. This is an optional step.
Tip If export.zip is not created for any reason, an email is sent to developers along with the migration log.
- On the day of staging in the migration process, the automated script picks up export.zip and import.xml to move objects to the staging environment.
- Upon successful testing in staging, the objects from DevOps are moved to the production environment using the automated scripts.
...