Run the Pipelines

Before you deploy your extension to the production instance, run the CSM pipeline to migrate configurations and the production sandbox pipeline to deploy extension to the sandbox where you migrated configurations.

You should run pipelines and jobs in this order:

1. Run the CSM pipeline to migrate configurations.

   Before you run the pipeline or the import configurations job, make sure that the source and the target instances match and the target instance does not have any configurations re-keyed or from another source.

2. Run the production sandbox pipeline to deploy the extension to the sandbox where you've migrated configurations.
3. Preview the sandbox and test the extension.
4. If the testing is successful, run the apply configuration job.

Follow these steps to run pipelines in the above order:

1. In the left navigator, click Builds .
2. Click the Pipelines tab.
3. On the right side of the CSM pipeline, click Build .
   Wait for configurations to migrate to the production Oracle Cloud Applications instance's sandbox. Click the pipeline's name to monitor the progress of its build jobs.
4. In the pipeline, if the import configuration job is successful, verify the migrated configurations in the sandbox's preview mode. Open the Oracle Cloud Applications production instance's migration page, click Incoming and click Preview.

   Here's an example:

   
   

   
   Description of the illustration oracleapps_imported_migrationset.png

   
   

   To find out on what you can see in the sandbox preview mode, see Preview Mode in Unified Migration in Configuring and Extending Applications.

5. Return to VB Studio's Build page.
6. Open the import configuration job's build log and note the CSM Sandbox ID. You'll need the sandbox ID when you deploy the extension to the sandbox.
   Here's an example:

   [2020-07-09 09:31:20] BACKUP_IN_PROGRESS...
   [2020-07-09 09:41:31] IMPORT_IN_PROGRESS...
   [2020-07-09 09:42:01] BACKUP_DONE...
   [2020-07-09 09:42:32] IMPORT_IN_PROGRESS...
   [2020-07-09 09:43:02] CSM Sandbox Id: abc01def2fe345fedcba12345ab01234
   [2020-07-09 10:26:46] IMPORT_SUCCESS...
   [2020-07-09 10:26:46] 

7. Click the Pipelines tab. On the right side of the production sandbox pipeline, click Build .
8. In the Configure Parameters dialog, enter the sandbox's name in the $<SANDBOX_NAME> format and click Build Now.
   Here's an example:

   
   

   
   Description of the illustration pipeline_sandbox_parameter.png

   
   
9. After the pipeline is successful, verify the extension along with the migrated configurations in the sandbox's preview mode. Open the Oracle Cloud Applications production instance's migration page, click Incoming and click Preview.
10. Return to VB Studio's Build page.
11. If the imported configurations meet your expectations, save the migration set.
    1. In the Jobs tab, open the export configuration job's build log and note the Configuration Migration Set ID.
       Here's an example:

       [2021-01-14 06:18:16] Status: Export Started
       [2021-01-14 06:18:16] Configuration Migration Set ID is 1234432100056789
       [2021-01-14 06:19:47] IN_PROGRESS...
       [2021-01-14 06:42:43] SUCCESS...
       [2021-01-14 06:46:19] CREATED...

    2. Open the apply configuration job and click Build Now.
    3. In the Configure Parameters dialog box, enter the configuration set ID and click Build Now.
       After saving the configurations on the production instance, if you want to revert to the previously saved instance, run a build of the restore configuration job.
12. Deploy the extension to the production mainline. See Set Up the Project to Deploy to Production in Administering Visual Builder Studio.

After you apply the configurations, Oracle Cloud Application end users won't see any changes to the user interface until they log out and log back in to the App.