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, merged to your project's main branch and then directly deployed to your target instance without a pipeline. You can change both the default target branch to merge to (something other than main), as well as the CI/CD pipeline setting for the target branch. (If you change the target branch and you want to deploy with a pipeline, you'll have to create a pipeline for that branch first.) 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 a branch-level setting that impacts everyone who publishes to that branch when collaborating on the extension, including those working on the extension 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. Under Building and Publishing, select a default Target Branch in your workspace's remote repo. (Click to refresh the list of remote branches, as needed.)

   When others publish to this remote branch, you'll be notified so you can refresh your workspace to pick up their changes. This target branch is also preselected in the Publish dialog when you publish your extension, but you can change it.

3. If a pipeline exists for the selected target branch, the Enable CI/CD pipeline checkbox displays.

   Select or deselect Enable CI/CD pipeline:

   • The option is enabled when at least one packaging job is enabled for the target branch. Deselect the option to stop using CI/CD pipelines for publishing.

     With the CI/CD pipeline disabled, your extension's sources are merged to the target branch of the workspace's Git repository, selected when you click Publish, then built and deployed directly to the Oracle Cloud Applications instance within your Development environment.

   • The option is disabled when all packaging jobs for the target branch are disabled. When you click Publish, your extension is merged to the target branch, then built and deployed directly to your Development environment's Oracle Cloud Applications instance.

     Select the option to start using CI/CD pipelines for publishing. Selecting the option enables all pipelines associated with the repository's selected target branch.

   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, see Publish Your Changes Through CI/CD Pipelines or Publish Your Changes Without CI/CD Pipelines.