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.

Extensions are, by default, merged to your remote repository's main branch and then deployed directly to your target Oracle Cloud Applications instance—without a CI/CD pipeline.

CI/CD pipelines, on the other hand, 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 required, you can change the CI/CD pipeline setting for the target branch.

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.

Click Menu in the upper right corner and select Settings.
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.) This branch will be preselected in the Publish dialog when you publish your extension, but you can change it in the dialog.

In addition, when others publish to this target branch in the remote repo, you'll be notified so you can refresh your workspace to pick up their changes.

If the new target branch doesn't yet have a pipeline and you want to use one for deployment, click Create CI/CD Pipeline to create and enable build jobs and a pipeline for the branch. In the deployment job that's created, the deployment target is always the environment associated with the workspace, but you can change it, if needed.
If a pipeline exists for the selected target branch, the Enable CI/CD pipeline checkbox displays.

By default, the option is disabled. (The default setting takes effect when you create a new workspace through the Edit Page in Visual Builder Studio link in version 25.01.1 or later. If you create a workspace through the New Application Extension menu option on the Workspaces page, the default setting takes effect in version 25.10 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.)

Select or deselect Enable CI/CD pipeline, as needed:
- 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. You'll need to do this, for example, if you want to deploy your changes to other Oracle Cloud Applications instances, such as to a test or production instance.
  
  The option remains 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 is merged to the target branch, selected when you click Publish, then built and deployed directly to your Development environment's Oracle Cloud Applications instance.
  
  The option remains disabled when all packaging jobs for the target branch are disabled.
If a CI/CD pipeline doesn't exist (for example, because you created a branch for developing a feature and have not yet created a pipeline, or if you pushed a scratch repo to a remote repo and chose not to create a pipeline), this option won't show.

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.