Enable or Disable the CI/CD Pipeline for Publishing

Extensions are typically published through continuous integration and delivery (CI/CD) pipelines, which 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 Development environment.

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 header and click 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. Because deployment happens immediately, you won't have a chance to create a merge request as part of the publishing process. So if you want to get your changes reviewed, create a merge request before publishing your changes.

   • 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.

• If you've disabled the CI/CD pipeline, your changes are merged from your working branch to the main branch, then immediately deployed to the Development environment associated with your workspace. Simply click the link in the Publish dialog to see your published changes:
  
  
  Description of the illustration publish-pipelinedisabled.png
  
  

  Make sure you copy and paste the deployment URL to your clipboard before you click Close. You won't have access to the URL after the Publish dialog is closed.

• If you've enabled the CI/CD pipeline, your changes are merged from your working branch to the main branch, then deployed to the Development environment as defined in the pipeline that's enabled for the main branch.