Enable or Disable the CI/CD Pipeline for Deployments

Your visual application can be deployed to a Visual Builder instance either directly or via continuous integration and delivery (CI/CD) pipelines. The default setting for new workspaces is to deploy directly to the Visual Builder instance in the environment associated with your workspace—without a pipeline.

CI/CD pipelines, on the other hand, give you the option of deploying a visual application 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 visual applications 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 deploys to that branch when collaborating on the visual application. Before you enable or disable the pipeline, make sure it's the optimal configuration for all those who work on the visual application. 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 Refresh Remote Branches to refresh the list of remote branches, as needed.) This branch will be preselected when you click Publish to deploy your visual application, but you can change it in the Publish dialog.

    In addition, when others deploy 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.

  3. 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 in version 25.10 or later. Existing visual applications continue to use the CI/CD pipeline setting that was previously set in the Settings editor, until you change it.)

    Select or deselect the Enable CI/CD pipeline, as needed:

    • Select the option to start using CI/CD pipelines for deployments.

      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 Visual Builder 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 deployments.

      With the CI/CD pipeline disabled, your visual application'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 Visual Builder instance in the environment associated with your workspace.

      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.

    For information about creating and configuring the build jobs and pipelines for any additional Visual Builder instances you want to deploy to, see Deploy to Test and Production Instances.

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: