Enable or Disable the CI/CD Pipeline for Publishing

When your extension is published, your changes can be deployed to the Oracle Cloud Applications instance in your Development environment either directly or via continuous integration and delivery (CI/CD) pipelines.

CI/CD pipelines give you the option of deploying an extension to multiple environments as well as automating some lifecycle operations (for example, you can deploy dependent artifacts to the target environment in parallel or delete extensions to clean up the environment). If this extended functionality is not required, you can opt to disable the CI/CD pipeline and simply publish the extension to your environment.

Configuration changes made in your Oracle Cloud Application (through the Edit Page in Visual Builder Studio link) are, by default, deployed directly to your target instance. If you want, you can change the default by enabling the CI/CD pipeline for your extension. (The default setting takes effect when you create a new workspace in version 25.01.1 or later. Existing extensions continue to use the CI/CD Pipeline setting that was previously set in the extension's Settings editor—until you change it.)

Caution:

The CI/CD pipeline is an extension-level setting that impacts everyone collaborating on the extension, including those using it in Express mode. Before you enable or disable the pipeline, make sure it's the optimal configuration for all those who work on the extension. Once you decide on a setting, it's a good idea not to change it unless your requirements change significantly.
  1. Click Menu in the upper right corner and select Settings.
  2. Toggle CI/CD Pipeline under Publishing as needed:

    • The setting is ON when at least one packaging job in your environment is enabled. Toggle OFF the setting to stop using CI/CD pipelines for publishing.

      With the CI/CD pipeline disabled, your extension's sources are merged to the default branch (main) of the workspace's Git repository, then built and deployed immediately to the Oracle Cloud Applications instance within your Development environment.

    • The setting is OFF when all packaging jobs in your environment are disabled. Toggle ON the setting to start using CI/CD pipelines for publishing. Toggling ON the setting enables all pipelines associated with the repository's default branch (main).

    As with most other actions, any change you make is logged to the activity stream on the Project Home page.

When you're ready to merge your changes, publish your extension.