Publish Your Changes

When you and your team members have finished testing your work, it's time to kick off the publishing process so your changes can be applied to your Oracle Cloud Applications instance within your development environment.

To publish your work (which in VB Studio is referred to as an "extension"):

1. Click Publish in the Designer's header:
   
   
   Description of the illustration express-designer-publish-changes-action.png
   
   
2. If you have changes that haven't been saved to the underlying repository, enter a brief comment describing your changes when prompted, then click Publish:
   
   
   Description of the illustration express-publish.png
   
   

   Your view of the Publish dialog may be different based on some advanced settings. If you're asked to enter a commit message instead (as shown here), it means your administrator has set things up so that all changes are first reviewed and approved by a developer, who will actually look at the code representing your changes. To get your changes reviewed, enter a message in Commit Message, add at least one reviewer if no name is specified, then click Publish:
   
   Description of the illustration express-branchprotected.png
   

3. If prompted, re-enter your user name and password for the Oracle Cloud Applications instance you're working with and click Add Credentials and Continue.

At this point, you'll be notified that your changes were successfully published. Click the environment link to see your deployed changes. (Make sure you open the link or copy its location to your clipboard before you click Close. You won't have access to it after the Publish dialog is closed.)

Description of the illustration express-nopipeline.png

Tip:

If you'd like to publish your changes to an Oracle Cloud Applications instance other than the one you're working in, click the link to the Manage Extension Lifecycle page. See Manage Your Published Extensions.

Note:

If you don't see a link to your environment, it's likely that your extension uses continuous integration and delivery (CI/CD) pipelines for deploying your changes. In this case, you'll see notifications indicating that the publish process is progressing:

Description of the illustration express-buildnotifications.png

When publishing is complete, you can go to the Oracle Cloud Applications instance in your environment to see your changes.

Publishing via CI/CD pipelines gives you the flexibility for advanced lifecycle operations, such as adding extra steps to the out-of-the-box configuration or using shell scripts against a target environment. If this isn't required, switch to the Advanced mode and disable the CI/CD pipeline.

IMPORTANT: To see the changes you just made, your users will have to sign out of the Oracle Cloud Applications instance, then sign back in again to be certain they're seeing the latest.