Set Up the Project to Deploy to Production
By default, a project deploys extensions to the Development environment, which is the Oracle Cloud Application instance you were using when you clicked Edit Page in Visual Builder Studio. Follow these steps to deploy to the PROD instance, so users can deploy to it after their development and test cycles are complete.
The Oracle Cloud Applications PROD instance resides in a different identity domain from the DEV and TEST instances, which means you’ll need the URL for the PROD instance, as well as user credentials that VB Studio can use to deploy to this instance. These credentials must be those of a local user, not a federated identity, and must not require multi-factor authentication.
To set up a project to deploy to PROD:
- Add the PROD instance to an environment
- Create a production branch
- Create and configure production build jobs
- Configure the pipeline so that the packaging and deployment jobs run in succession
- Run the production pipeline.
Tip:
For a simpler interface where you can manage the lifecycle of all your extensions, use the Manage Extension Lifecycle page. From this single page, you can deploy extensions to your PROD instance without the need to create build jobs and pipelines, as long as that instance has an authentication method of OAuth.